Supabase, the managed version is nice. This is not a critique, just what has worked for me, hoping it helps other people as well.

If this repo has helped you, star it.

The self-hosted version leaves a lot to be desired. This repo is an attempt to document convenient workarounds.

Feel free to submit your via a pull request.

Configuring authentication:

In the supabase hosted version we have a convenient UI for the "Authentication" tab like so:

In the self-hosted version we have just this one:

A significant downgrade in convenience.

To navigate to the same URLs (provided you use the Supabase CLI, running on - http://127.0.0.1:54323/project/default/)

• Sign In / Up menu - http://127.0.0.1:54323/project/default/auth/providers
• Sessions - http://127.0.0.1:54323/project/default/auth/sessions
• Rate Limits - http://127.0.0.1:54323/project/default/auth/rate-limits
• Emails - http://127.0.0.1:54323/project/default/auth/templates
• Multi factor - https://supabase.com/dashboard/project/default/auth/mfa
• URL configuration - https://supabase.com/dashboard/project/default/auth/url-configuration
• Auth protection - https://supabase.com/dashboard/project/default/auth/protection
• Advanced - https://supabase.com/dashboard/project/default/auth/advanced

Redirect URLs on sign in (OTP, Oauth):

After signing up up a user with OTP and trying to redirect them to a specific page.

For example "localhost:3000/dashboard", you are likely to just get redirected to "localhost:3000".

In the hosted version, you have a very nice UI. That is disabled in the self-hosted one.

To configure in config.toml: site_url = "env(FRONTEND_DASHBOARD_URL)"

A list of exact URLs that auth providers are permitted to redirect to post authentication.

additional_redirect_urls = ["env(FRONTEND_URL)"]

Where in .env you have: FRONTEND_URL="http://localhost:3000" FRONTEND_DASHBOARD_URL="http://localhost:3000/dashboard"

Doing just: site_url = "env(FRONTEND_URL)/dashboard" will resolve to just "/dashboard", which is not nice.