-
-
Notifications
You must be signed in to change notification settings - Fork 300
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Use MySQL/MariaDB/Postgres instead of SQLite #954
Comments
You can set the Feel free to test other db flaors and lmk how it goes. I'll close the issue for now |
Okay, here's what i did... In the obico-web container, i dumped the database:
Then i created a MySQL (actually MariaDB) user and database and updated the
and restarted the In theory, this would the create the DB schema in the MySQL DB and all i would have to do then would be import the data again, via:
... and of course afterwards restart all other containers to switch to the new DATABASE_URL. But unfortunately the image i'm using (thanks @gabe565) does not include the
Could you guys maybe add |
Please open a PR for it. Adding the dependency is easy but testing and making sure it works entails a lot more work. This is something I hope you can do as part of the PR. |
I managed to build an image with
So the main problem is:
The PR would be this one: #955 |
I have a solid dislike for SQLite, mostly because i prefer to just have my DB backup solution do its job, instead of me having to add another file to my file-based backup solution. But i of course get why starting of with SQLite makes sense for "simple" deployments.
As you seem to be using
dj-database-url
, it should theoretically be possible to just use one of the RDBMS mentioned in the title, but before switching over and migrating or starting with a new blank database, i was wondering if there are any known issues with any of them, or any other reason why sticking to SQLite is mandatory.I don't think you guys are running the hosted service on SQLite, either ;-)
Thanks for any feedback!
The text was updated successfully, but these errors were encountered: