Railway Deployment #19cb4f fix: normalize alembic db url scheme#86
Merged
Conversation
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
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.
Problem
The pre-deploy Alembic migration crashed with ModuleNotFoundError: No module named 'psycopg2'. apps/api/alembic/env.py passed the raw postgresql:// URL to engine_from_config and context.configure, which SQLAlchemy defaults to the psycopg2 dialect, but only psycopg v3 is installed.
Solution
Reused the existing _normalize_db_url helper from app.core.db to rewrite the URL to postgresql+psycopg:// before setting sqlalchemy.url and in run_migrations_offline, matching the fix already applied to the runtime engine in db.py.
Changes
apps/api/alembic/env.pyContext
eead718Generated by Railway