Repository navigation
supabase-dashboard 0.2.0-dev.1
Pre-releaseWhat's new
A project's pages are now its own Supabase Studio. The read-only table editor from 0.1.0-dev.3 and 0.1.0-dev.4 is gone. Members open the stack's Studio through the dashboard instead, from the project page, the project cards, or the switcher. Each project's Studio is served on its own host under SUPABASE_DASHBOARD_STUDIO_DOMAIN. Every request is checked against a dashboard session, and the dashboard adds the gateway's Studio login on the server. Owners, admins, and developers can open Studio; viewers can't, because Studio gives full database access and shows the stack's keys. Signing in from a Studio link returns to Studio. See "Studio access" in the deployment guide.
- An optional Studio access log (
SUPABASE_DASHBOARD_STUDIO_ACCESS_LOG_DAYS, off by default) records who opened which project's Studio. It can be paged through, filtered by member, and exported as CSV. - The bundled Caddy obtains a certificate for each project's Studio host the first time someone opens it, and only for registered projects.
Health checks run on a schedule and keep a week of history. The server checks each project every 15 minutes by default (SUPABASE_DASHBOARD_HEALTH_CHECK_INTERVAL_MINS, 0 turns it off). The project overview shows recent checks as a day-by-hour grid. Checks now cover Storage, Realtime, Edge Functions, and Studio's route as well as Auth and REST. Reported versions are compared with the tested ones. Failed checks say where to look next for gateway, TLS, and DNS problems. A gateway certificate that has expired or expires within 30 days is flagged on the overview, the project cards, and the administrator page.
Connecting a stack is guided. Registering a project leads to a setup page with the steps in order: API keys, certificate, Studio login, first check. The overview lists each service's address and which key it takes. A stack behind a private certificate authority can be trusted for every project (SUPABASE_DASHBOARD_EXTRA_CA_FILE) or for one project from its settings page.
Other changes
rotate-secret-keymoves stored credentials to a new encryption key while the old one stays readable. Steps are under "Replacing the encryption key" in the deployment guide.- Installation admins can connect a Dokploy instance with an API key on the administrator page. The key is checked against Dokploy first, then stored encrypted. Nothing is deployed through Dokploy yet.
- Upstream's Envoy gateway and the new
sb_publishable_/sb_secret_API keys are tested alongside Kong and the JWT keys. - More refused operations are written to the audit log.
Upgrading from 0.1.0-dev.4
- Back up the metadata database.
- Replace
compose.yamlandCaddyfilewith the files from the new Docker bundle. Both changed, for the Studio hosts. - Set
SUPABASE_DASHBOARD_VERSION=0.2.0-dev.1, thendocker compose pull && docker compose up -d. Migrations run on startup. - To use Studio, set
SUPABASE_DASHBOARD_STUDIO_DOMAIN, add a wildcard DNS record for it, and save each stack gateway's Studio login on the project's Settings page. Until a login is saved, the project page warns every member. Then change the stack'sDASHBOARD_PASSWORDso the dashboard is the only way into its Studio ("Closing the stack's own Studio entrance" in the deployment guide).
Known limitations
- Studio's Realtime inspector and Storage uploads go from the browser straight to the stack's public API URL, not through the dashboard. Members' browsers must reach that URL, and anyone who can open Studio can read the service role key there.
- The per-project Studio certificates count toward the certificate authority's rate limits (Let's Encrypt: 50 per registered domain per week), and each Studio host name appears in certificate transparency logs. A wildcard certificate avoids both but needs a DNS provider plugin.
- Realtime and Studio don't report a version, and analytics can't be reached through upstream's gateways.
- The Dokploy connection is only a connection: no stacks are created, adopted, or removed through it yet.
Install
Container image (linux/amd64, linux/arm64):
docker pull ghcr.io/filipnone/supabase-dashboard:0.2.0-dev.1
To deploy on a Linux server with Docker, download supabase-dashboard-0.2.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.1.0-dev.4...v0.2.0-dev.1