what is the correct to handle auth like this

I have installed using docker, but none of the URLS work

actually which URL to use ? which port ?

3000, 8000 return some JSON

5000 returns this

{
  "message": "Route GET:/ not found",
  "error": "Not Found",
  "statusCode": 404
}

Self-hosted supabase ports: - Storage: 5000 - REST: 3000 - Realtime: 4000 - Postgres: 5432 - Auth: 9999 - Kong: 8000 Port 8000 (Kong) is the service which routes to all other services, via endpoints like

/rest/v1

,

/realtime/v1

, etc. There's an example nginx config which shows how they route at https://dev.to/chronsyn/self-hosting-with-supabase-1aii

and the admin panel ?

The dashboard isn't open source yet. An open-source version is being worked on in the

/feat/studio

branch on the main Supabase repo

shoot. i wanted that tbh.... is there an ETA to the open source version >

I don't think so - last time I checked a few weeks ago, it's still very early in development. If we can spur people to contribute to it though, it'll definitely help get it released much more quickly.

how can i help ? any guides or something ?

In supabase the mail goes to spam, so link isn't there

when I mark it as not spam and try again then it work

any way to fix it

when im trying to delete the user account in auth, this is the output.

means you can't delete because there are some objects owned by the user in objects

ahh i see

maybe i delete the data from my storage avatar first

thanks man, ill try this

thanks man. you are right. 🙂 big help

Okay thanks

np

Is there a way to implement business logic in the hosted version?

Hi people, db noob here, do anyone know why i'm getting this error?

https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403 is related to authorization. Can you share the query itself as well?

I actually followed Nader's 6 minute supabase setup video and got inspired to checkout supabase. would this suffice? https://github.com/zeshhaan/supabase-first-time/blob/main/pages/index.js

How to handle password resets

Getting a weird 404 error when trying to do a simple update with the client api