Logflare exposed without much notice in docs when self hosting, and how would I add basic auth to it?

Improve documentation


This is as much a question as a suggestion for improvement. I am not familiar with neither supabase nor digital ocean where I am "self hosting" a supabase instance. I just recently started to poke around for learning purposes.

Link


Link to [documentation](

Describe the problem


I used the droplet template provided by digital ocean to spin up a supabase instance and link a domain to the studio. I find it a bit odd that the logflare instance isn't behind basic auth like the dashboard by default, isn't this a potential security risk?

I tried adding

to the supabase/docker/volumes/api/kong.yml file but it didn't seem to have an effect, the :4000 endpoint is still totally public

Describe the improvement


I'd expect at least a notice that the service is exposed, and suggestions on how to secure it.