-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There are unnecessary options in the .env.sample for self-hosting #26578
Comments
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. |
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:
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. |
Add note in studio settings from .env.sample for self-hosting
Add note and remove Studio settings from .env.sample for self-hosting
Remove Studio settings from .env.sample for self-hosting supabase#26578
Remove Studio settings from .env.sample for self-hosting
Improve documentation
Link
/docker/.env.sample
Describe the problem
Self-hosting does not support the use of Studio. However, the sample includes this option.
Describe the improvement
Remove settings related to Studio.
Additional context
Since Studio cannot be used in self-hosting, it is necessary to remove the description to prevent confusion among users. Alternatively, a detailed explanation should be provided.
The text was updated successfully, but these errors were encountered: