Repository navigation
DRU-749 -- Ship the Alembic configuration and core migrations inside the druks package - #830
Merged
czpython merged 1 commit intoOct 5, 2026
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
…the druks package
czpython
force-pushed
the
paulo/dru-749-include-alembic-configuration-and-migrations-in-the-druks
branch
from
October 5, 2026 06:53
1fde118 to
b821010
Compare
czpython
deleted the
paulo/dru-749-include-alembic-configuration-and-migrations-in-the-druks
branch
October 5, 2026 07:06
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
A wheel or sdist install of
drukscould not rundruks init-db:database.pyresolvedalembic.inione level above the package, and neither the ini nor the core migration tree was in the distribution.alembic.iniandmigrations/move frombackend/intobackend/druks/, so the wheel and sdist carry them anddatabase.pyreads the ini next to itself. Source checkouts, editable installs, and the image resolve the same path. Revision files move unchanged, so the schema and history stay the same.Core migrations now sit at
<package>/migrations/versions, the same layout an app ships. The developer command isuv run alembic -c backend/druks/alembic.ini ….