Supabase
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.
JoinSupabase
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.
JoinEmail not considered as provider if user already uses SSO?
-e with-supabase. The app is meant to be in two parts, a /dashboard that needs to have email login, and other routes (say /google or /github) that can only be accessed to users who linked their google or github account.
When doing some tests, I noticed that if I first sign in through /dashboard, then go to /github -> no issue, both appear as providers in my supabase admin. However, if the users signs in for the first time through /github, then goes to /dashboard in the future and signs in using email, they can "sign up" but they receive no email with a confirmation link (likely because they technically already exist), they can only "sign in" and for this need to request a new password. At this point they do receive the email and are able to log in, however I do not see email being added as a provider. Do you know how to handle that by any chance?...Pass custom application_name on connection
URGENT: Project Restoration Failed - Core Services Unhealthy After Extended Period
Project Access / Team members
Enable RLS on Storage.Objects
missing FROM-clause entry for table "new"
Database is stuck in "pausing" state for 2 days
Does deleting an Organization cancel all subscriptions?
Is the Supabase Pro Plan Required for Looker Studio?

SupaBase Dedicated Backend
Discord OAuth not working on iOS / Safari
Can not login to my account
LOCAL setup db error: No suitable key or wrong key type
Cloudflare Blocking All Signup/Login Requests
403 Forbidden errors with "CORS header 'Access-Control-Allow-Origin' missing" on ALL signup attempts from web origins. Log in works.
...Is there a need to put my migration within an transaction between `BEGIN;` / `COMMIT;` statements.
supabase stop --no-backup though when we merged it in and deployed the 2nd and 3rd transactions were not applied.
It is not ideal that it behaves differently locally using supabase cli and when finally deploying! Or should I just not use any BEGIN; / COMMIT; statements in future at all so I don't make this mistake again.
Edit: added detail....Lost tables
Log in help
domain hook-up
Supabase Auth without middleware
Having trouble figuring out how to read headers in an edge function request
req.headers?