Goal
Decide on the database engine for the project and create the schema tables.
See the full design in docs/database-design.md.
Options
- Option 1 — Start on SQLite, switch to PostgreSQL for deployment
- Dev: SQLite (zero setup, Django default)
- Prod: PostgreSQL (best Django fit, handles the daily batch + concurrent users)
- Option 2 — Use PostgreSQL from the start (local + prod)
- Run Postgres locally (e.g. via Docker) so dev and prod match
- Avoids subtle SQLite↔Postgres differences (case sensitivity, etc.)
Both engines are free; MySQL was considered but skipped (Postgres is the Django standard).
Decision
Tasks
References
- Schema + engine comparison:
docs/database-design.md
Goal
Decide on the database engine for the project and create the schema tables.
See the full design in
docs/database-design.md.Options
Both engines are free; MySQL was considered but skipped (Postgres is the Django standard).
Decision
Tasks
DATABASESinsettings.pypip install psycopg2-binary+ add DB env varsUSERS,FAVOURITE_JOBS,SAVED_SEARCHES,DEMAND_SNAPSHOTS,JOB_POSTINGSReferences
docs/database-design.md