TL;DR
- prisma migrations production
- For PostgreSQL apps with frequent model changes.
Who this is for
- For PostgreSQL apps with frequent model changes.
Keyword (SEO)
- prisma migrations production
Safety rules
- Add first, use later
- Don’t change types blindly
- Backup before migration
Two-step deployments
- Deploy code for both states
- Then clean up
- Have a rollback plan
Common pitfalls
- Dropping columns immediately
- Missing indexes
- No staging tests
Branchly: migrate on a branch, not on production
In DevStudio projects we evolve the Prisma schema on PostgreSQL in Branchly — a separate database branch (like Git) for features, staging, and migration tests. Production gets prisma migrate deploy only after review; up to 5 parallel branches make safe testing without touching client data. The app connects via DATABASE_URL from the Branchly panel; runtime runs on DevStudioIT Cloud.