[FEATURE] add alembic migrations #31

New issue

Closed

opened 2026-07-12 19:29:47 +00:00 by kkmlmust · 0 comments

kkmlmust commented

2026-07-12 19:29:47 +00:00

Collaborator

Is your feature request related to a problem?
Currently, database schema are not figured at all. This approach is error-prone, lacks version control, makes it difficult to sync schema across team members, and provides no rollback capability. When working with Docker Compose, there's no standardized way to apply migrations automatically on container startup.

Describe the solution you'd like
Integrate Alembic for database migration management with:

Auto-generation of migrations from SQLAlchemy model changes using alembic revision --autogenerate
Seamless integration with Docker Compose (run migrations as a separate service or via docker-compose run)
Support for uv package manager (add alembic via uv add)
Environment-based database configuration (DB_HOST, DB_USER, etc.) for Docker flexibility
Version-controlled migration history in Git

Describe alternatives you've considered

Using raw SQL scripts stored in a folder — no version tracking, no rollback
Running migrations manually via alembic locally — not reproducible in Dockerized environments
Using Flask-Migrate or Django migrations — not suitable for FastAPI/SQLAlchemy projects

Checklist

I have checked that this feature is not already requested
I am willing to help implement it (optional)

**Is your feature request related to a problem?** Currently, database schema are not figured at all. This approach is error-prone, lacks version control, makes it difficult to sync schema across team members, and provides no rollback capability. When working with Docker Compose, there's no standardized way to apply migrations automatically on container startup. **Describe the solution you'd like** Integrate Alembic for database migration management with: - Auto-generation of migrations from SQLAlchemy model changes using `alembic revision --autogenerate` - Seamless integration with Docker Compose (run migrations as a separate service or via `docker-compose run`) - Support for uv package manager (add alembic via `uv add`) - Environment-based database configuration (DB_HOST, DB_USER, etc.) for Docker flexibility - Version-controlled migration history in Git **Describe alternatives you've considered** - Using raw SQL scripts stored in a folder — no version tracking, no rollback - Running migrations manually via `alembic` locally — not reproducible in Dockerized environments - Using Flask-Migrate or Django migrations — not suitable for FastAPI/SQLAlchemy projects **Checklist** - [ ] I have checked that this feature is not already requested - [ ] I am willing to help implement it (optional)

kkmlmust added this to the Sprint 1 milestone

2026-07-12 19:29:47 +00:00

kkmlmust added the

backend

label

2026-07-12 19:29:47 +00:00

kkmlmust self-assigned this

2026-07-12 19:29:47 +00:00

kkmlmust referenced this issue from a commit

2026-07-12 23:40:45 +00:00

feat: add alembic migrations base

kkmlmust referenced this issue from a pull request that will close it,