There are unnecessary options in the .env.sample for self-hosting about supabase HOT 3 OPEN

I understood. Currently one docker-compose.yaml deploys one Supabase instance, not management plane of Supabase.

I guess Self hosting guide can be improved in two ways:

1. Present deployment diagram: to clarify what resources will reader get after deployment
2. Clarify the scope of self-hosted dashboard: Self-hosted dashboard is deployed at instance level, which implies the following.

• User cannot perform deployment tasks using Dashboard
• Each Supabase instances must be deployed separately

Studio readme does mention point 2, but it is better to notice readers the limitations upfront instead of expecting them to do their own experiments.

from supabase.

Self hosting does support Studio but without hosted Supabase features such as project management. What leads you to conclude that the self-hosted version cannot be used with Studio?

from supabase.

In the provided Docker Compose example, I noticed that the studio has no exposed ports. When I force the connection through port 3000, it ultimately redirects to the same screen as the web interface on port 8000, which is specified under kong.

I understood that the studio is a tool for creating and managing multiple instances (with self-hosting not supporting multi-instance management), and kong is a tool for using these instances.

If the studio refers to a web UI, then I have misunderstood its concept. The Docker Compose configuration seems somewhat confusing for first-time users.

The options related to the studio mentioned above intrigue me and prompt experimentation. However, it is not documented that self-hosting does not support the studio (here referring to the multi-instance management functionality). This information can only be inferred from discussions, indicating that the feature's documentation is not clear.

#4907

from supabase.