Feature request

the problem

Naming containers in docker-compose makes it impossible to have two supabase projects side by side

While exploring supabase locally I had the problem that I needed to spin up another supabase setup to verify if I messed up my current setup. Due to the setting the container_name in docker-compose.yml it is not possible to spin up another instance without getting an error that this name is already in use.

It is nice to have a defined container name, but I don't see any benefit except for easier identification when running docker ps or docker container ls.

the solution

Maybe the cli can create a random name and prefix it with supabase-.

the alternative

The only alternative here is ejecting the project or editing the files in .supabase/ manually