Local Project Management
I have Supabase running on a development server in my home for building and testing. I have multiple Projects and it is my understanding that running it locally each "Project" needs to be a complete separate Supabase Stack. Unlike the cloud version, where it allows you to create projects from the Studio Dashboard, you can't do this or like this locally.
Is there no way to manage all projects from a single interface like the cloud Studio Dashboard?
Is there no way to manage all projects from a single interface like the cloud Studio Dashboard?
22 Replies
Not that i'm aware of. Most people i think run
supabase start for each project repositoryno, each project will be a separate stack
so would it be easier to copy my docker-compose.yml and .env file and spin up a new stack
you'll have to change container names in the second compose file
then it should work fine
correct
and ips
you mean ports?
i have static ips set
You can setup a reverse proxy in front of all instances
i am in the process of setting up Traefik
If you decide to use nginx or caddy, you can take a look at this script https://github.com/singh-inder/supabase-automated-self-host
might help you to setup config for traefik
I think I understand now. I develop on my laptop, but my supabase is installed on my server in the basement.
Yeah it should work fine. I'd recommend to look at the config which is generated from the script I linked above. That will definitely help
and I dont do things from command line for writing an app, so the supabase start part was confusing
i just opened the link
thank you!
thats for supabase cli
so i dont need to use supabase cli to make this work
You can use that too. But its meant to be used in dev environment. Let me confirm if we can change kong's ports when using cli.
we are testing building apps with Claude Code, so we just need to give it the api information and auth information. it "should" do everything else
You can change the ports for kong and studio
https://supabase.com/docs/guides/local-development/cli/config#api.port https://supabase.com/docs/guides/local-development/cli/config#studio.port
What cli does is create container names based on the directory config is created in
So for example: you have this directory path
/first-stack/supabase/config.toml , supabase cli will create container names: supabase_auth_first-stack. By default it uses the directory name. Can be changed by modifying project_id field in config.toml
All the config is done via config.toml when using cliok, so if i understand, I am basically doing the same thing just manually by copying the docker compose and changing the information in that file
absolutely. internally its doing the same thing
that makes MUCH MORE SENSE NOW
THANK YOU!!!!!
no problem. Let me know if you have any other questions
just remembered, you'll also need to change port for inbucket service. It is named inbucket but it actually uses mailpit image. Its exposed on port 54324 so make sure to change that as well when setting up > 1 stack
https://supabase.com/docs/guides/local-development/cli/config#inbucket.port