Repository navigation
supabase-dashboard 0.3.0-dev.1
Pre-releaseWhat's new
Stacks can be created through Dokploy. With a Dokploy instance connected, owners and admins can create a new Supabase stack from the organization's Projects page. They pick a name, a host, and a Dokploy environment the organization may use. The server generates the stack's database password, JWT secret, keys, and Studio login, then creates a compose service from a pinned compose file, deploys it, and registers the project once it's up. The job runs in the background, one saved step at a time, so a dashboard restart resumes it instead of creating a second stack. Any member can follow it on the job's page. Dokploy keeps the stack's variables in its own database, so anyone with access to the service in Dokploy can read its secrets.
- Installation admins confirm which Dokploy service the dashboard itself runs in. The dashboard finds it by matching its public host against Dokploy's domains.
- Installation admins choose which Dokploy environments and servers each organization may use. An organization with none of its own uses the dashboard's environment, as long as the dashboard's service is confirmed.
- The deployment can supply the Dokploy URL and key (
SUPABASE_DASHBOARD_DOKPLOY_URL,SUPABASE_DASHBOARD_DOKPLOY_API_KEY_FILE).
Provisioned stacks can be run and changed from the dashboard. The overview of a provisioned project shows its Dokploy service, the service's status, and the five newest deployments.
- Owners and admins can stop, start, and redeploy it.
- Removing it from Dokploy keeps its data volumes. Destroying it deletes them too, and only owners can do that. Both need the project's name typed, and the project stays registered either way.
- Owners and admins can change seven Auth and API settings (site URL, redirect URLs, sign-ups, email confirmation, anonymous sign-ins, token lifetime, exposed schemas). A review lists the variables that change and the services that restart before anything is written.
- Variables edited in Dokploy since the dashboard wrote them are listed by name, and a settings change stops instead of overwriting them. Owners and admins can accept the edits.
Existing stacks in Dokploy can be adopted. Owners and admins can list the Supabase compose services in their allowed environments and register one as a project. Its keys are copied only when they tick the box. Nothing is written to Dokploy.
Other changes
- The administrator page lists provisioning and stack jobs that failed in the last 30 days.
rotate-secret-keyalso reseals the secrets of unfinished jobs and the records of variables written to provisioned stacks.
Upgrading from 0.2.0-dev.1
- Back up the metadata database.
- Set
SUPABASE_DASHBOARD_VERSION=0.3.0-dev.1, thendocker compose pull && docker compose up -d. Migrations run on startup.compose.yamlandCaddyfiledidn't change. - To create stacks, connect Dokploy on the administrator page, confirm the dashboard's own service, and allow targets for each organization.
docs/dokploy.mdhas the details.
Known limitations
- Only Dokploy v0.31.x is supported, tested with v0.31.1.
- The Dokploy key's expiry can't be shown: no Dokploy call says which key made the request.
- Routing Studio hosts to a dashboard running inside Dokploy needs a Traefik dynamic file. It's documented but hasn't been tried end to end.
- A new stack has no mail server, so its sign-ups are closed and users are added from Studio. SMTP settings aren't editable yet.
- HTTPS for a new stack hasn't been run against a real certificate authority. The end-to-end run used plain HTTP.
- Adoption hasn't been tried with a stack made from Dokploy's own Supabase template.
Install
Container image (linux/amd64, linux/arm64):
docker pull ghcr.io/filipnone/supabase-dashboard:0.3.0-dev.1
To deploy on a Linux server with Docker, download supabase-dashboard-0.3.0-dev.1-docker.tar.gz, unpack it, and follow its README. Nothing is compiled on the server.
The *-linux-gnu.tar.gz files contain the same server binary and web assets for running without Docker (glibc 2.36 or newer).
This is a development pre-release. Expect breaking changes between dev releases. Database migrations only move forward: back up the metadata database before upgrading, and do not downgrade.
Full Changelog: v0.2.0-dev.1...v0.3.0-dev.1