Cannot self host two supabase instances at the same time

[andrybicio]

Bug report

• [ x ] I confirm this is a bug with Supabase, not with my own application.
• [ x ] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

Cannot have two self hosted supabase instances running at the same time as container_name value are equal.

To Reproduce

Simply clone two supabase projects and try to spin the containers up after commenting or remapping the values in ports key of the original docker compose.
Note that if those are commented, then one has to expose port 8443 and 8000 of kong service.

Expected behavior

Like the supabase-cli, after running the docker-compose up -d in the main folder, I expect that the either the project name or any unique identifier is appended to the container name so that names do not conflict.

After making some research, even though services have the same name (e.g., kong), they should not conflict with each other as long as they stay in different networks. A possible solution is to use aliases for the service to distinguish them if they happen to be in the same network, like for example if using a reverse proxy.
However, the vector service loads the declarative config file volumes/logs/vector.yml, makes use of the docker container_name to make the routing of the logs.

This is somehow related to
supabase/cli#28

[singh-inder]

You're facing this issue because container_name is hardcoded in docker-compose.yml files. For your second instance, you will have to edit the container_name for all services manually. supabase cli generates container config dynamically suffixing project_id.

[andrybicio]

Yes, indeed that's how I fixed it. The problem is that the vector config is hardcoding the container_name too. It would suffice to add an environment variable PROJECT_NAME (set as default to supabase) that dynamically sets the container_name and that is passed to the vector service, whose configuration dynamically replaces ${PROJECT_NAME}-kong, ${PROJECT_NAME}-studio etc.
I might create a repo for this, but I would prefer this to be done automatically with an environment variable. That shouldn't break too many things

[singh-inder]

Ya, this would make things easier for setting up multiple instances on same server.

[andrybicio]

@singh-inder I created this repo with a small docs, with everything I found out. Hope this can be helpful!
Please let me know if something can be improved or changed
https://github.com/andrybicio/supabase-multiple-self-hosting

[Hallidayo]

Hi @andrybicio - thanks for opening this one and for your repo. I'll move this over as a discussion so other users can see. Thanks again!