Using the proper Supabase local development flow is the best way to provide the most accurate context of your Supabase project! Learn how to get started with Supabase locally in this video:

So I have to run like 8 different services in docker to use supabase in development?

YouTube link here:

im still confused. when you do supabase link... does that write some config to the supabase directory? or can i have multiple projects linked at one time? im vibecoding a bunch of different projects and can't figure out how to keep them separated

not sure 'most accurate context' holds for edge functions. mine behaved fine locally but threw weird cors errors in prod for weeks. did you find a reliable way to mirror that behavior before deploy?

@supabase There is still no way to use branching or multiple Supabase in parallel locally. Providing some sort of solution would greatly improve workflow with Agents running locally

Local dev's essential if you're doing anything with RLS, but most people skip it and wonder why policies work in production but not their laptop. The real gain isn't the accuracy though,it's not waiting 40 seconds per deploy to catch a typo.

@supabase When working with multiple work streams at once - it’s easier to use Supabase in the cloud and branches. Is it possible to have multiple instances of Supabase running locally or it’s not a common or supported scenario ?