3 ms·
It’s normal Postgres. There’s no need to handle everything on the front end. The tutorials nudge you to learn RLS and use their SDKs for the client, but you can
by scosman 2y ago
It’s normal Postgres. There’s no need to handle everything on the front end. The tutorials nudge you to learn RLS and use their SDKs for the client, but you can write perfectly normal server side code as well.
- teaearlgraycold 2y agoYeah I’ve ran a small project where I just did everything with the “service account” credentials which operates like a normal Postgres connection.
- balls187 2y agoIf you're not supporting users, it's fine. But if you usecase involves Supabase auth, using a service account to bypass RLS is kind of like hardcoding connection strings.
- scosman 2y agoYou can use both properly and together. The service account should only be accessed on the service. If using Auth+Server, you can check the verified user identity via Auth JWTs (or something, see the docs). Yeah, don't use the server connection on the client, but they have many warnings against that.