Hi! First off, thanks for making this project. There's been so much conversation about using SQLite in production, and it's really nice to have a library that includes a good baseline of default settings.
The next release of dsd-railway, a plugin for django-simple-deploy, will include support for SQLite using dj-lite. Default deployments will set up a Postgres database, but the following command will set up a persistent volume with a SQLite database:
$ python manage.py deploy --automate-all --db sqlite
It was really straightforward to incorporate dj-lite into dsd-railway, and I'm planning to add similar functionality to most existing django-simple-deploy plugins.
I'm wondering what's likely to happen to a project that uses dj-lite for its initial deployment, and then upgrades the library at some later point. For most libraries we upgrade locally, run tests, and then upgrade the deployed decencies. But upgrading a library that specifies database settings feels a little different.
I imagine there are upgrades that could be made to dj-lite that would be completely safe to incorporate into an existing deployed project at any point, which would leave the project in a better state. I also imagine there are some upgrades where the maintainer might need to be more careful about whether or not to include those configuration changes, or how to go about including them.
Is this a significant thing to consider, or am I overthinking this?
Hi! First off, thanks for making this project. There's been so much conversation about using SQLite in production, and it's really nice to have a library that includes a good baseline of default settings.
The next release of dsd-railway, a plugin for django-simple-deploy, will include support for SQLite using dj-lite. Default deployments will set up a Postgres database, but the following command will set up a persistent volume with a SQLite database:
It was really straightforward to incorporate dj-lite into dsd-railway, and I'm planning to add similar functionality to most existing django-simple-deploy plugins.
I'm wondering what's likely to happen to a project that uses dj-lite for its initial deployment, and then upgrades the library at some later point. For most libraries we upgrade locally, run tests, and then upgrade the deployed decencies. But upgrading a library that specifies database settings feels a little different.
I imagine there are upgrades that could be made to dj-lite that would be completely safe to incorporate into an existing deployed project at any point, which would leave the project in a better state. I also imagine there are some upgrades where the maintainer might need to be more careful about whether or not to include those configuration changes, or how to go about including them.
Is this a significant thing to consider, or am I overthinking this?