Can you turn off the exposed docker ports when using the Supabase CLI and a config.toml file?

[jtdevops]

Hi,

There is an open-source project that I am using that utilized the Supabase CLI.

When you start the application using 'supabase start' multiple docker containers and a docker network are created.
I am using NGINX Proxy Manager (as a reverse proxy) in a docker container and I have it connected it to this supabase docker network which I can use to restrict access to the Supabase Studio UI. However with this port exposed, users could directly access the Studio UI without going through NGINX Proxy Manager.

Is it possible to turn off or disable the exposed container ports for all Supabase docker containers?

I have attempted to comment out the 'port' configurations, but there is a default port assigned if one is not provided in the config.toml file.

Any help in being able to secure this would be greatly appreciated.

Regards,
Justin.

[jtdevops]

I just discovered that I should be using the Self-Hosted Docker environment instead.