Replies: 2 comments 1 reply
-
Hey, I'm self-hosting a Wakapi instance only for myself, using the default database, I'd be more than happy to (try) to help. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Awesome, thanks a lot in advance! 🙌 Anyone who's keen on testing right now, please do this:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
👋 I'm looking for two or three people who are willing to test new pre-releases of Wakapi on their own, self-hosted instance.
Background: Wakapi features both unit- and API tests, but, admittedly, both are not super comprehensive. Some testing is still manual. Plus, over the last months and years of development, it has turned out that the biggest error sources in Wakapi are (a) the different databases supported and (b) database schema migrations. Often times, things work fine in my dev environment or on Wakapi.dev, but then fail at some of your self-hosted instances. These failures are often caused by using a different DBMS, operating system or CPU architecture (...), by upgrading from a different (older?) Wakapi version or simply by some rare edge case represented in your data.
Before a new release that includes changes to the core logic, I test quite extensively on MySQL, using a dump from Wakapi.dev (only containing my own data). On Postgres and SQLite I only test very briefly.
It would be super helpful to me, if there was a small pool of Wakapi self-hosters (preferably with different databases), who - when asked to - do no more than pull the latest pre-release code, compile it, try to run it, briefly click through the dashboard and report back any errors that come up while doing so. Preferably, you'd backup your DB before, just in case 😉.
If you like to participate, just drop a quick comment here and subscribe to the topic 👇.
Beta Was this translation helpful? Give feedback.
All reactions