Apply migrations on startup via migrate deploy#16
Merged
Conversation
The container entrypoint used `prisma db push`, which syncs the schema directly and cannot run data-preserving migrations — e.g. adding a NOT NULL column to a populated table fails, and migration backfills never run. Switch to `prisma migrate deploy` so committed migrations (incl. the signing-log decoupling backfill) apply correctly on deploy. Pre-existing databases must be baselined once with `prisma migrate resolve --applied <migration>` for the already-present schema before the first deploy with this entrypoint.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The container entrypoint used
prisma db push, which syncs the schema directly fromschema.prismaand cannot run data-preserving migrations — adding a NOT NULL column to a populated table fails, and migration backfills (like #15's signing-log denormalization) never run.Switch to
prisma migrate deployso committed migrations apply correctly on deploy.Operational note: pre-existing databases (managed by
db push, no_prisma_migrationstable) must be baselined once before the first deploy with this entrypoint: