Repository navigation
supabase-dashboard 0.3.0-dev.5
Pre-releaseWhat's new
Password reset by email. With mail set up, the sign-in page has a "Forgot your password?" link that emails a link to choose a new password. The link lasts an hour and works once, and it stops working when a newer one is sent or the password changes. Each account gets at most three links an hour. The page answers the same way, and takes about as long, whether or not the account exists. Using the link signs the account out everywhere and revokes its API tokens. Without mail, supabase-dashboard-server reset-password on the server still works.
Resend. The dashboard can send its email through Resend's HTTP API instead of SMTP. Set SUPABASE_DASHBOARD_RESEND_API_KEY_FILE (or SUPABASE_DASHBOARD_RESEND_API_KEY) in place of the SMTP_* settings; setting both is refused. The From address has to be on a domain verified in Resend. See "Invitation email" in docs/deployment.md.
Resending invitations. Owners and admins can send an open invitation again from the Team page. It gets a new link for the same address and role, the old link stops working, and the send is in the audit log as organization.invitation_resend.
Flat Studio hosts. SUPABASE_DASHBOARD_STUDIO_DOMAIN also accepts a pattern such as *-studio.example.com. Each project's Studio is then at <project id>-studio.example.com, one level under example.com, so a *.example.com DNS record and certificate cover it. That includes Cloudflare's free certificate on a proxied record, which doesn't cover <id>.studio.example.com. The dashboard's own host must not match the pattern. With the bundled Caddy, change the Studio site's address to *.example.com (see the note in Caddyfile). The existing studio.example.com form works as before.
Stack settings for Auth's email. On a stack the dashboard created or adopted through Dokploy, owners and admins can set Auth's mail server from Stack settings: host, port, username and sender address. The password, SMTP_PASS, can be set or removed in a write-only field. The page only says whether it's set, and the value never comes back to the browser, the job record, the audit log or the server log. The compose file now points the links in Auth's emails at /auth/v1/verify through the gateway.
GitHub and Google sign-in for a stack. In the same section, owners and admins can turn on GitHub and Google sign-in for the stack's users and set each provider's client ID and secret. The secret is write-only like SMTP_PASS. The page shows the callback URL to register with GitHub or Google. A provider can't be turned on without a client ID and a secret.
Stacks created before this release run a compose file that doesn't read the new variables, so those settings show as locked there.
Dokploy install guide. It now explains how to create the first operator from the dashboard container's terminal in Dokploy.
Upgrading from 0.3.0-dev.4
- Back up the metadata database.
- Set
SUPABASE_DASHBOARD_VERSION=0.3.0-dev.5, thendocker compose pull && docker compose up -d. The server applies one migration at startup, which adds the table for password reset requests. - To use Resend, add the key from the new lines in
.env.exampleand mount it as a Compose secret, the same way as the SMTP password.
Known limitations
- No email has been sent through a real mail server from a managed stack's Auth, or through the real Resend service. Both were tested against local stand-ins.
- GitHub and Google sign-in haven't been tried with a real OAuth app.
SMTP_PASSand the provider secrets can't hold spaces, quotes,$,#, backslashes or backticks when set from the dashboard; set such values in Dokploy. There's no setting for the sender name yet.- Removing a secret writes an empty value; the variable stays in the stack's settings in Dokploy.
- Flat Studio hosts are tested in the server against a mock gateway, not yet behind Cloudflare or another real proxy.
Container image (linux/amd64, linux/arm64):
docker pull ghcr.io/filipnone/supabase-dashboard:0.3.0-dev.5
To deploy on a Linux server with Docker, download supabase-dashboard-0.3.0-dev.5-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.4...v0.3.0-dev.5