Has anything changed recently? ~1year ago I installed a local instance (that I still use today for logging LLM stats) and IIRC all I had to do was "docker compose up". All the dockers are still starting for me at boot from that 1yo install, to this day. (I use it on 127.0 so no SSE & stuff, perhaps that's where the pain points are? Dunno, but for my local logging needs it's perfect).
This isn't documented anywhere. Deep deep in their GitHub issues you'll find a script for generating this magic string which needs to be set as an environment variable.
See https://github.com/supabase/supabase/issues/17164#issuecomme...
I admit, I already had a working mail server and wildcard LE cert... let's say you'd need the other half of the day too to set that up if wanted.
Personally I set it up in a way such that the studio is not publicly accessible but can be accessed using ssh port forwarding.
All in all, I still agree that it's not really user friendly to self host it. It's basically only one supabase project. But in reality, it shouldn't be that hard to create new template dbs in postgres to set up multiple projects and also provide a good UI for that. They don't bother to provide that functionality though for I believe obvious reasons.
Just recently the docker-compose stack from the current main branch would not start properly, because someone committed a faulty health check. Why does this make it to the main branch, does nobody there review PR?
Starting a new stack is nothing compared to maintaining it. Upgrading to newer images requires carefully checking which environment variables suddenly appeared in new versions or maybe were renamed. Upgrades never really went absolutely smooth for me in the past.