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
Rate limiting for supabase has been a longstanding feature request for many users using their postgrest client. Nuxt supabase is in a unique position to solve this issue, as it can utilize the power nuxt server routes to proxy postgrest requests with an added rate limiter. All the user has to do is enable it and direct whitelist data requests only coming from the nuxt server.
There exists a rate limiting guide on supabase itself, but this is far from ideal, as it cannot protect any read requests and it adds serious overhead since rate limit state is stored in the database.
The text was updated successfully, but these errors were encountered:
Rate limiting for supabase has been a longstanding feature request for many users using their postgrest client. Nuxt supabase is in a unique position to solve this issue, as it can utilize the power nuxt server routes to proxy postgrest requests with an added rate limiter. All the user has to do is enable it and direct whitelist data requests only coming from the nuxt server.
There exists a rate limiting guide on supabase itself, but this is far from ideal, as it cannot protect any read requests and it adds serious overhead since rate limit state is stored in the database.
The text was updated successfully, but these errors were encountered: