What problem does it solve?
It solves the friction and risk of managing a Supabase project’s database schema, auth, RLS, and serverless functions by providing a consistent local-first workflow that keeps production changes controlled and reviewable.
Core Features & Use Cases
- Local-first Supabase CLI workflow: initialize projects, link to a remote project, start/stop the local stack, and pull existing schema to keep environments aligned.
- Migration-driven database evolution: generate diffs or create migrations directly, review SQL before applying, and push migration history to staging/production.
- Security patterns (RLS + auth linkage): enable RLS, define least-privilege policies, and structure tables that reference
auth.users for owner-only access.
- Edge Functions + Storage basics: scaffold and deploy Deno-based functions with auth context, and set up storage buckets/policies for safe file access.
Use case: A team needs to add a new table and ensure only authenticated users can read/update their own records—use migrations plus RLS policies to implement the change locally, review the generated SQL, then push it to the remote environment.
Quick Start
Use the supabase CLI to start your local stack, create or edit migrations for your schema change, then run a database reset locally and push the migrations to your Supabase project.