Repository navigation
supabase-dashboard 0.3.0-dev.3
Pre-releaseWhat's new
API tokens. Every operator can create, list and revoke their own API tokens under Account, API tokens. A token is shown once; the dashboard keeps only its hash. Tokens expire after 7, 30, 90 or 365 days, and an account can hold 25 working tokens at a time. Disabling an account stops its tokens, and a password reset revokes them. Creating and revoking a token are recorded in the account audit log.
Read-only API. GET /api/v1/organizations, /api/v1/organizations/{org_id}/projects and /api/v1/projects/{project_id} answer requests that carry Authorization: Bearer <token>. They never accept the session cookie. A token acts as its account with the account's current roles, limited to its scopes (organizations:read, projects:read), and it can't change anything, open Studio or read keys. See docs/api.md.
Installing on Dokploy. deploy/dokploy-compose.yaml runs the dashboard as a Dokploy compose service with its own metadata database, and "Installing the dashboard on Dokploy" in docs/dokploy.md walks through it. Dokploy stores file mounts, the encryption key included, in its own database and writes them to the server as world-readable files; the guide says what that means for who can read the key.
Upgrading from 0.3.0-dev.2
- Back up the metadata database.
- Set
SUPABASE_DASHBOARD_VERSION=0.3.0-dev.3, thendocker compose pull && docker compose up -d. A migration adds theapi_tokenstable on startup.
Known limitations
- Requests with a bad token aren't rate limited or audited. Tokens are 256 random bits, so guessing one isn't practical.
- Token lists stop at 100 entries and have no paging yet.
- The Dokploy install was tested against a disposable Dokploy v0.31.1 with the 0.3.0-dev.2 image, through its API. It hasn't been tried with a real certificate, through Dokploy's web UI, or across an upgrade.
Container image (linux/amd64, linux/arm64):
docker pull ghcr.io/filipnone/supabase-dashboard:0.3.0-dev.3
To deploy on a Linux server with Docker, download supabase-dashboard-0.3.0-dev.3-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.3.0-dev.2...v0.3.0-dev.3