Workaround · Permissions & security · Blocks work
Uses Supabase only as hosted Postgres reached by own backend
1 source thread · first seen 2024-01
Summary
To avoid RLS risk, the user stopped using the auto API and uses Supabase just as a managed Postgres that only their backend connects to.
- Affects
- Developers concerned about public table access
- Workaround
- Host a normal Postgres on Supabase and connect only from a backend
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“I now just use Supabase to host a normal Postgres that only my backend connects to”