Skip to content

docs: add Alembic troubleshooting to README #39

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.

Sign up for GitHub

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

Open
Youdahe123 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: add Alembic troubleshooting to README #39

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -782,6 +782,18 @@ npm run dev

---

## Alembic troubleshooting

- Run `alembic current`, `alembic heads`, and `alembic history` to confirm the database, migration files, and revision graph match.
- If you see `Can't locate revision identified by 'xxx'`, the DB is pointing at a migration that is no longer in your checkout; in local dev, reset the schema and rerun `alembic upgrade head`.
- If `alembic upgrade head` succeeds but tables still look missing, verify the app and Alembic are using the same `DATABASE_URL`.
- If autogenerate misses changes, check `alembic/env.py` and make sure `Base.metadata` is imported before `context.configure(...)`.
- If multiple heads appear, inspect the branch history with `alembic heads` and merge or resolve the divergent revisions before continuing.

For the full setup and troubleshooting guide, see `docs/DEVELOPER_SETUP.md`.

---

## Configuration Reference

All configuration is via environment variables (loaded from `.env`):
Expand Down
Loading