More step by step workflow videos like these for multi-tenant Authorization as well! This makes so much sense now in terms of creating a local vs prod project. Thanks!
I feel like the cuts cause information to be conveyed incorrectly. 4:28 - CC:`Because RLS blocks everything by default. Secure. But just for the select action.`. Which I hope is not true. I think/hope the [But] sentence is in reference to your specific policy which was maybe just a bad cut in the video???
@@1youngtai Make whatever changes you want in your local supabase instance in the browser UI then run 'npx supabase db pull' it will check for differences between what's in the database now and what's in your migrations. Then it will automatically create a "remote_schema" migration in your project codebase.
@rtorcato > does the supabase editor create migrations too? It would be cool if it would add the migrations to a project's repo as a commit. That's exactly how we thought it could work in the long term.
More step by step workflow videos like these for multi-tenant Authorization as well! This makes so much sense now in terms of creating a local vs prod project. Thanks!
"Branching is an early access only feature, which must not be used in a production setting."
You made a very dry subject *super* interesting. Thank you!
Dumb question: so the seed file only runs if it’s not the main branch?
I feel like the cuts cause information to be conveyed incorrectly.
4:28 - CC:`Because RLS blocks everything by default. Secure. But just for the select action.`. Which I hope is not true. I think/hope the [But] sentence is in reference to your specific policy which was maybe just a bad cut in the video???
Im a abit simple so does this create multiple copies of your databasr and the data inside ?
I hope branching will be prod-ready soon! Such a game-changer
does the supabase editor create migrations too? It would be cool if it would add the migrations to a project's repo as a commit.
You can use the CLI to diff you DB state against the DB state described in the migration and automatically create a new migration to match them.
@@funkdefied1 how?
@@1youngtai Make whatever changes you want in your local supabase instance in the browser UI then run 'npx supabase db pull' it will check for differences between what's in the database now and what's in your migrations. Then it will automatically create a "remote_schema" migration in your project codebase.
@rtorcato
> does the supabase editor create migrations too? It would be cool if it would add the migrations to a project's repo as a commit.
That's exactly how we thought it could work in the long term.
Supabase is backed for startups.
Amazing!
Very nice
mark zuckerburg is on show with jhon, explaining the new features of meta