Replace prisma db push with versioned migrations #16

New issue

Closed

opened 2026-10-14 23:16:44 -04:00 by vmanne-poc · 0 comments

vmanne-poc commented

2026-10-14 23:16:44 -04:00

Owner

The backend container runs prisma db push --accept-data-loss on start. That's fine for development but unsafe in production: a schema change can silently drop columns and there's no history of changes.

Plan: baseline the current schema as the first migration, switch the container to prisma migrate deploy, and document the workflow in docs/internal/operations.md.

The backend container runs `prisma db push --accept-data-loss` on start. That's fine for development but unsafe in production: a schema change can silently drop columns and there's no history of changes. **Plan:** baseline the current schema as the first migration, switch the container to `prisma migrate deploy`, and document the workflow in `docs/internal/operations.md`.

vmanne-poc added this to the Phase 9: Migrations & bounce handling milestone

2026-10-14 23:16:44 -04:00

vmanne-poc added the

feature

label

2026-10-14 23:16:44 -04:00

vmanne-poc referenced this issue from a commit

2026-10-15 00:59:25 -04:00

Versioned database migrations replace prisma db push

vmanne-poc referenced this issue from a pull request that will close it,

2026-10-15 00:59:43 -04:00

Phase 9: migrations, account controls, frontend tests, SES bounces #24