Phase 5: Database migration tooling#10
Merged
Merged
Conversation
- Accept --env flag (dev, staging, prod) to target different environments - Auto-discover all migration files in supabase/migrations/ sorted by name - Skip seed data for prod environment (migrations only) - Load env-specific files (.env.dev, .env.staging) with .env.local fallback - Add db:setup:dev, db:setup:staging, db:setup:prod npm scripts Closes #5 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
scripts/setup-database.jsto accept--envflag (dev, staging, prod).sqlmigration files insupabase/migrations/in sorted order (no more hardcoded paths)prodenvironment (migrations only).env.dev,.env.staging) with.env.localfallbackdb:setup:dev,db:setup:staging,db:setup:prodUsage
Test plan
npm run buildpasses (verified)node scripts/setup-database.js --env invalidexits with error (verified)node scripts/setup-database.js --env prodshows "Seed data: no (production)" and discovers all migrations (verified)Closes #5
🤖 Generated with Claude Code