9
Git-based Schema Management w/ Supabase CLI
Source: supabase/supabase#4692 · opened by @devstein
Hi 👋 First off, want to say thank you for Supabase and all your open source work! I love the way you all have been building the product and keep finding myself thinking how intuitive it is. Along those lines, I read [this blog post about migration management with Supabase CLI]( and have a similar strong preference for automated schema diffing rather than manual migrations. I've been playing around with the Supabase CLI and I would like suggestions on how to achieve the following workflow and if this approach makes sense. 1. The source of truth for the database (non-supabase managed) schemas live in Git: db/schemas/*, db/triggers/*, etc 2. To make changes to the DB, users modify the db/ directory and apply the changes to a fresh local Postgres instance - Essentially running supabase start but initializing the schema to the db/ directory rather than the state of remote 3. Users use the Supabase CLI to generate the migration, validate it, then push it to the remo…
No pledges yet. Be the first to back this.
Comments
Similar requests
Default schema for Foreign Keys
1 vote · 0 comments
Manage API Exposed Schemas with Supabase CLI or Management API
7 votes · 0 comments
Restrict database schema changes in web UI
13 votes · 0 comments
Table Editor UX: unclear table selection
2 votes · 0 comments
Allow selecting a schema in database connection string settings
4 votes · 0 comments
No comments yet.