ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Cloud & infrastructure · #supabase
A concise architecture note covering requirements, minimal design, trust boundaries, operational checks, failure modes, and redesign triggers for Supabase RLS using auth.uid().
Stop relying on application-level filtering to protect data. Learn how to use Supabase Row Level Security (RLS) to move authorization into the database and prevent leaks.
Learn how to secure your Supabase tables with Row‑Level Security: enable RLS, create per‑user policies, test with the JS client, and verify policies in PostgreSQL. A step‑by‑step guide with code snippets and recovery tips.
Learn how to add OAuth login with Google or GitHub, embed role claims in the JWT via Supabase Admin API, and read those claims in Edge Functions for fine‑grained access control.
Stop writing middleware for basic authorization. Learn how to use Supabase Row Level Security (RLS) to move your access control directly into Postgres for a more secure, scalable API.
Goal: achieve identical schema migration outcomes when running Supabase CLI locally via supabase start and in a CI pipeline that uses supabase db push against a temporary project. Constraints: the CLI does not automatically remove ephemeral Supabase projects created for CI, requiring manual cleanup to avoid quota limits, and the Docker images pulled by supab
Supabase migration CLI and transaction scope The Supabase CLI’s supabase migration apply runs all SQL statements in a single transaction by default. When a migration includes large DDL changes—such as adding an index to a table with millions of rows—this transaction can acquire an exclusive lock on the target table. The lock may prevent concurrent SELECTs, l
After a Supabase migration fails with the error “relation already exists”, the CLI records the last good version in supabase_migrations but it is unclear whether it automatically removes any temporary database objects that were created during the failed run. The documentation does not guarantee cleanup of orphaned indexes, constraints or other schema artifac
postgresql