You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Supabase studio (admin dashboard) in production mode needs to protect via Authentication,
Therefore the easiest way to restrict access is to set auth_basic in the Nginx config.
No. With connection pooling, many users can share a few database connections, you can have 10 connections serving a 1000 users. This is because in a web application the web users are not hitting the database constantly(GUI work, idleness, etc) and when they need to, they "borrow" a connection, fulfill a request and then "return" the connection to the pool.
Use Supabase as a back-end service,
We need two instances of Supabae! one for production, the other one for the stage.
Resource: https://supabase.com/docs/guides/self-hosting/docker
The text was updated successfully, but these errors were encountered: