feat: Move alembic config into mealie package for easier distribution #4329
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does / why we need it:
The Alembic configuration and database migration scripts are moved inside the mealie Python package. This means they will be always available, in a consistent location. The advantages are:
ALEMBIC_CONFIG_FILE
environment variable doesn't need to be set, ever. I've left it in as an option for people who still want to use it.As a side effect,
ruff
(specificallyisort
) no longer thinksalembic
is a project ("LOCALFOLDER") package, so the imports ofalembic
are moved to the third-party group.Which issue(s) this PR fixes:
This is one task from discussion #4322.
Testing
I built and ran the Docker container, then made sure the database migration still occurred.
I created a database change following the instructions in database-changes.md.