Files
boker/migrations
SowinskiBraeden 882726e5e9 fix: correct migration chain for league settings columns (2.5.1)
Migration 0003_league_settings was chained to 0002 but the DB was already
at 0003_site_admin (an applied migration with no version file). Added a stub
for 0003_site_admin to satisfy the chain and updated the down_revision on
0003_league_settings accordingly. Columns eligible_min_sessions and
break_even_cents now apply cleanly on top of the existing schema.
2026-06-26 21:43:32 -07:00
..
2026-06-23 21:38:33 -07:00
2026-06-23 21:38:33 -07:00
2026-06-23 21:38:33 -07:00
2026-06-23 21:38:33 -07:00

Single-database Alembic environment managed through Flask-Migrate.

Install dependencies with:

    pip install -r requirements.txt

Then run migrations with:

    flask --app app db upgrade

For a quick local development bootstrap without Alembic, the app also exposes:

    flask --app app init-db