Matt Johnston
34c2092a62
On a deployment where `NIMBUS_PROD_PROJECTS_URL` is supplied to the build but not to the function runtime, testing an edge function fails with a 400, "Provided URL is not a valid Supabase edge function URL", while the CSP on the same page already allows the projects domain. The two readers run at different times. `csp.ts` is imported by `next.config.ts` and evaluated during the build, so it sees the value. `lib/api/edgeFunctions.ts` is evaluated inside the API route at request time, where the variable is absent, so `isValidEdgeFunctionURL` falls through to the default `<ref>.supabase.(co|red)` check and rejects every projects URL. Declaring the variables under `env` pins both readers to the same build-time value: `getNextConfigEnv` turns each key into a `process.env.<key>` define, and `getDefineEnv` applies those to every compilation rather than only the client, so the pages API route gets the substitution too. This is a no-op where the variables are unset — `getNextConfigEnv` skips null values, leaving `process.env.*` as an ordinary runtime lookup for self-hosted and OSS builds. The values are wildcard domains that already appear in the public CSP header, so inlining them into the client bundle exposes nothing new.
Supabase Studio
A dashboard for managing your self-hosted Supabase project, and used on our hosted platform. Built with:
What's included
Studio is designed to work with existing deployments - either the local hosted, docker setup, or our CLI. It is not intended for managing the deployment and administration of projects - that's out of scope.
As such, the features exposed on Studio for existing deployments are limited to those which manage your database:
- Table & SQL editors
- Saved queries are unavailable
- Database management
- Policies, roles, extensions, replication
- API documentation
Managing Project Settings
Project settings are managed outside of the Dashboard. If you use docker compose, you should manage the settings in your docker-compose file. If you're deploying Supabase to your own cloud, you should store your secrets and env vars in a vault or secrets manager.
How to contribute?
- Branch from
masterand name your branches with the following structure{type}/{branch_name}- Type:
chore | fix | feature - The branch name is arbitrary — just make sure it summarizes the work.
- Type:
- When you send a PR to
master, it will automatically tag members of the frontend team for review. - Review the main contributing guide to help test your feature before sending a PR.
- The Dashboard is under active development. You should run
git pullfrequently to make sure you're up to date.
Developer Quickstart
Note
Supabase internal use: To develop on Studio locally with the backend services, see the instructions in the internal
infrastructurerepo.
# You'll need to be on Node v22
# in /studio
## For external contributors
pnpm install # install dependencies
pnpm run dev # start dev server
## For internal contributors
## First clone the private supabase/platform repo and follow instructions for setting up mise
mise studio # Run from supabase/platform alongside `mise infra`
## For all
pnpm run test # run tests
pnpm run test -- --watch # run tests in watch mode
Running within a self-hosted environment
Follow the self-hosting guide to get started.
cd ..
cd docker
docker compose -f docker-compose.yml -f ./dev/docker-compose.dev.yml up
Once you've got that set up, update .env in the studio folder with the corresponding values.
POSTGRES_PASSWORD=
SUPABASE_ANON_KEY=
SUPABASE_SERVICE_KEY=
Then run the following commands to install dependencies and start the dashboard.
npm install
npm run dev
If you would like to configure different defaults for "Default Organization" and "Default Project", you will need to update the .env in the studio folder with the corresponding values.
DEFAULT_ORGANIZATION_NAME=
DEFAULT_PROJECT_NAME=