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.
Learn how to subscribe to Supabase Realtime via WebSocket, configure RLS and permissions, and avoid common pitfalls. Includes a live code example, limits, and verification steps.
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
When migrating data from an external PostgreSQL instance to a Supabase project using the postgres_fdw extension, the transfer of table rows does not automatically synchronize the state of sequence generators. In a zero-downtime migration strategy, data is pulled into the target Supabase instance while the source continues to accept writes. If the target sequ
Our team runs a production Supabase project and wants alerting that is genuinely actionable. The platform exposes several distinct signal sources: query performance data built on pg_stat_statements, Auth audit events, connection pool saturation, and usage metrics for compute, bandwidth, and database size. Dashboard notifications cover some of this, while log
postgresql