Skip to content

Releases

supabase-dashboard 0.3.0-dev.7

Pre-release

Choose a tag to compare

@github-actions github-actions released this 15 Nov 22:48

What's new

Signing out of the provider signs out of the dashboard. The dashboard now supports OpenID Connect Back-Channel Logout 1.0. When an operator signs out of Authentik, Authentik sends a signed logout token to /auth/oidc/backchannel-logout. The dashboard then ends the sessions started by signing in through Authentik, and the Studio sessions opened from them. Password sessions of the same account stay signed in.

The token's signature, issuer, audience, age and logout event are checked, and a token with a nonce is refused. Each token works only once. The endpoint accepts no cookie, takes a form of at most 16 KiB, and is exempt from the same-origin check only for POST to that path. Each ended session is in the audit log as session.oidc_backchannel_logout, without the token. To turn it on, set the provider's Logout URI to https://<dashboard host>/auth/oidc/backchannel-logout with the Back-channel method; the startup log prints the URL. Checked in Chromium against Authentik 2026.8.5.

Admins can unlink an operator's identity. On the administrator page's account list, an installation admin can unlink another operator's OIDC identity after a confirmation that names the account. This ends only the sessions started with that identity, and it's audited. Admins unlink their own identity under Account settings, as before.

Upgrading from 0.3.0-dev.6

  1. Back up the metadata database.
  2. Set SUPABASE_DASHBOARD_VERSION=0.3.0-dev.7, then docker compose pull && docker compose up -d. One migration runs at startup. It records which provider sign-in started each session, so sessions that already exist aren't ended by a logout from the provider.
  3. To use back-channel logout, add the Logout URI in Authentik as above. Authentik must be able to reach the dashboard's public URL.

Known limitations

  • Used logout tokens are remembered in the dashboard's memory, so a restart or a second dashboard instance doesn't know about them.
  • Ending Studio sessions through a provider logout was tested against a mock provider, not with Authentik.
  • Provider groups don't map to organization roles yet, and only one provider can be configured.

Container image (linux/amd64, linux/arm64):

docker pull ghcr.io/filipnone/supabase-dashboard:0.3.0-dev.7

To deploy on a Linux server with Docker, download supabase-dashboard-0.3.0-dev.7-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.6...v0.3.0-dev.7

Full Changelog: v0.3.0-dev.6...v0.3.0-dev.7

supabase-dashboard 0.3.0-dev.6

Pre-release

Choose a tag to compare

@github-actions github-actions released this 15 Nov 21:48

What's new

Single sign-on through OpenID Connect. Operators can sign in through an OIDC provider such as Authentik. It's off unless SUPABASE_DASHBOARD_OIDC_ISSUER_URL is set, and passwords keep working with it on. A provider identity signs in only to the account it was linked to. Each operator links theirs under Account settings > Security after signing in with their password, and can unlink it there. The dashboard never finds, links or creates accounts by email, so the provider can't sign anyone up.

The sign-in uses the authorization code flow with PKCE, state and nonce, and checks the ID token's issuer, audience, signature and expiry through the openidconnect crate. The dashboard only contacts the issuer's own origin. It follows no redirects, uses no proxy, and limits the size and time of each answer. A sign-in that started in one browser can't be finished in another. The setup steps for Authentik, and the redirect URI to register, are in "Signing in with OIDC" in docs/deployment.md. The flow was checked in Chromium against Authentik 2026.8.5.

Changing the sign-in email. Under Account settings, operators can change the address they sign in with. They confirm their current password, and the dashboard emails a one-time link to the new address. The address changes only when that link is used, and the old address gets a notice. A link expires, works once, and stops working if a newer one is sent or the password changes. Confirming also cancels any password reset link sent to the old address. This needs mail set up; without it, the page says so.

Invitations after signing in. An invitee who already has an account but isn't signed in now comes back to the invitation after signing in, and no longer has to open the email link again. The invitation code stays in the browser's session storage until it's used and never appears in a URL or the server log.

Upgrading from 0.3.0-dev.5

  1. Back up the metadata database.
  2. Set SUPABASE_DASHBOARD_VERSION=0.3.0-dev.6, then docker compose pull && docker compose up -d. The server applies two migrations at startup: one for email change requests and one for linked OIDC identities.
  3. To turn on single sign-on, follow "Signing in with OIDC". The settings are in the new lines of .env.example, and the client secret goes in a Compose secret like the encryption key.

Known limitations

  • Signing out of the provider doesn't sign out of the dashboard yet (no back-channel logout), and provider groups don't map to organization roles.
  • Only one provider can be configured, and only through the deployment's settings.
  • A sign-in in progress is kept in the dashboard's memory. A restart cancels it, and several dashboard instances behind one address can't share it.
  • An installation admin can't unlink another operator's identity.
  • If the provider's callback fails, the page the operator was going to is lost.
  • Changing the email needs mail set up. The limit of five change requests an hour resets when the server restarts. Other sessions stay signed in after the change.

Container image (linux/amd64, linux/arm64):

docker pull ghcr.io/filipnone/supabase-dashboard:0.3.0-dev.6

To deploy on a Linux server with Docker, download supabase-dashboard-0.3.0-dev.6-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.5...v0.3.0-dev.6

Full Changelog: v0.3.0-dev.5...v0.3.0-dev.6

supabase-dashboard 0.3.0-dev.5

Pre-release

Choose a tag to compare

@github-actions github-actions released this 15 Nov 20:12

What'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

  1. Back up the metadata database.
  2. Set SUPABASE_DASHBOARD_VERSION=0.3.0-dev.5, then docker compose pull && docker compose up -d. The server applies one migration at startup, which adds the table for password reset requests.
  3. To use Resend, add the key from the new lines in .env.example and 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_PASS and 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

supabase-dashboard 0.3.0-dev.4

Pre-release

Choose a tag to compare

@github-actions github-actions released this 15 Nov 12:01

What's new

Invitation emails. With a mail server configured, the dashboard emails the invitation link to the invited address once the invitation is saved. The page still shows the link once and says whether the email went out. If the send fails, the invitation still works and you can send the link by hand; the dashboard doesn't retry. Each send is in the audit log as organization.invitation_email, without the message or the link. Mail is off unless SUPABASE_DASHBOARD_SMTP_URL is set. The connection always uses TLS (smtps://, or smtp:// with STARTTLS required), and the password is read from a file or a variable, never from the URL. See "Invitation email" in docs/deployment.md.

Integrations tab. The list of Dokploy environments on an organization's Integrations tab was indented without bullets and its two buttons didn't line up, because it shared a style with the admin page. It has its own styles now.

Dokploy install guide. The guide explains the bind source path does not exist: .../files/secret.key error: the secret.key file mount is missing, or its File Path isn't exactly secret.key.

Upgrading from 0.3.0-dev.3

  1. Back up the metadata database.
  2. Set SUPABASE_DASHBOARD_VERSION=0.3.0-dev.4, then docker compose pull && docker compose up -d. This release has no migration.
  3. To turn on invitation emails, add the SUPABASE_DASHBOARD_SMTP_* and SUPABASE_DASHBOARD_MAIL_FROM settings from .env.example, and the smtp_password secret, to your files. They're new in this release's .env.example and compose.yaml.

Known limitations

  • Password reset by email isn't implemented. Reset a forgotten password with supabase-dashboard-server reset-password on the server.
  • There's no Resend adapter and no way to resend an open invitation's email.
  • Mail settings on Dokploy are documented but haven't been tried there. They were tested with the server against Mailpit.

Container image (linux/amd64, linux/arm64):

docker pull ghcr.io/filipnone/supabase-dashboard:0.3.0-dev.4

To deploy on a Linux server with Docker, download supabase-dashboard-0.3.0-dev.4-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.3...v0.3.0-dev.4

supabase-dashboard 0.3.0-dev.3

Pre-release

Choose a tag to compare

@github-actions github-actions released this 15 Nov 11:22

What'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

  1. Back up the metadata database.
  2. Set SUPABASE_DASHBOARD_VERSION=0.3.0-dev.3, then docker compose pull && docker compose up -d. A migration adds the api_tokens table 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

supabase-dashboard 0.3.0-dev.2

Pre-release

Choose a tag to compare

@github-actions github-actions released this 15 Nov 09:18

What's new

Audit logs. Owners and admins can read their organization's audit log on its new Audit log tab. It lists who did what in the organization and its projects, refused attempts included, 50 events per page, and can be narrowed to one member. Every operator can also read their own log under Account, Audit log. It shows what they did, plus what happened to their account, such as a sign-in refused with their email or an administrator disabling it. Events hold no keys, passwords, or project data. Developers and viewers can't read the organization's log, and a refused attempt is itself logged.

Integrations tab. An organization's Integrations tab shows owners and admins whether Dokploy is connected and which Dokploy environments new stacks can go to, with links to create or adopt a stack.

Upgrading from 0.3.0-dev.1

  1. Back up the metadata database.
  2. Set SUPABASE_DASHBOARD_VERSION=0.3.0-dev.2, then docker compose pull && docker compose up -d. A migration adds the organization to existing audit events on startup. On a large audit table this takes a moment.

Known limitations

  • Events about projects that were unregistered before this release can't be traced back to an organization, so they don't show up in any organization's log.
  • Audit events are kept until someone deletes them from the metadata database. There's no retention setting yet.
  • The Integrations tab's list of targets hasn't been checked in a browser against a connected Dokploy, only the not-connected state.

Install

Container image (linux/amd64, linux/arm64):

docker pull ghcr.io/filipnone/supabase-dashboard:0.3.0-dev.2

To deploy on a Linux server with Docker, download supabase-dashboard-0.3.0-dev.2-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.1...v0.3.0-dev.2

supabase-dashboard 0.3.0-dev.1

Pre-release

Choose a tag to compare

@github-actions github-actions released this 15 Nov 08:54

What'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-key also reseals the secrets of unfinished jobs and the records of variables written to provisioned stacks.

Upgrading from 0.2.0-dev.1

  1. Back up the metadata database.
  2. Set SUPABASE_DASHBOARD_VERSION=0.3.0-dev.1, then docker compose pull && docker compose up -d. Migrations run on startup. compose.yaml and Caddyfile didn't change.
  3. To create stacks, connect Dokploy on the administrator page, confirm the dashboard's own service, and allow targets for each organization. docs/dokploy.md has 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

supabase-dashboard 0.2.0-dev.1

Pre-release

Choose a tag to compare

@github-actions github-actions released this 12 Nov 21:48

What'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-key moves 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

  1. Back up the metadata database.
  2. Replace compose.yaml and Caddyfile with the files from the new Docker bundle. Both changed, for the Studio hosts.
  3. Set SUPABASE_DASHBOARD_VERSION=0.2.0-dev.1, then docker compose pull && docker compose up -d. Migrations run on startup.
  4. 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's DASHBOARD_PASSWORD so 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

supabase-dashboard 0.1.0-dev.4

Pre-release

Choose a tag to compare

@github-actions github-actions released this 08 Nov 12:33

What's new

Tables in the Table editor now open on a Data tab that shows their rows, 50 per page, with Previous and Next. The column list from 0.1.0-dev.3 moved to a Definition tab. Every member can read rows, viewers included. Nothing can be edited yet.

The dashboard reads rows through the stack's postgres-meta (/pg/query behind the gateway) with the service role key saved on the Settings tab. The key stays on the server. The server writes the query itself: one SELECT in a read-only transaction with a 5 second statement timeout. Table and column names come from postgres-meta and are always quoted, and nothing typed in the browser goes into the SQL.

Pages are sorted by primary key. A table without one is read in no fixed order, and the page warns that pages can overlap while the table changes. If the database hits the 5 second limit, the page says so instead of showing a generic error.

Upgrading from 0.1.0-dev.3

Pull the new image. There are no new migrations or configuration settings.

Known limitations

  • Rows are read with postgres-meta's database role, which in a standard stack bypasses row-level security. Anyone who can open the project sees every row.
  • Each value is cut to 200 characters, and only the first 50 columns are shown. The Definition tab still lists all of them.
  • Paging stops at page 2000 (100,000 rows). Later pages of a large table get slower, since PostgreSQL reads every earlier row first.
  • No filters, sorting, or row editing. Views, foreign tables, and foreign key details aren't shown.
  • Earlier limits still apply: up to 1000 tables per schema and 500 schemas, schemas with a comma in the name can't be opened, and only the Kong gateway is tested.

Install

Container image (linux/amd64, linux/arm64):

docker pull ghcr.io/filipnone/supabase-dashboard:0.1.0-dev.4

To deploy on a Linux server with Docker, download supabase-dashboard-0.1.0-dev.4-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.

supabase-dashboard 0.1.0-dev.3

Pre-release

Choose a tag to compare

@github-actions github-actions released this 08 Nov 12:02

What's new

Projects have a Table editor tab. Pick a schema to see its tables, then pick a table to see its columns: type, default, constraints, enum values, and description. It also shows the primary key, whether row-level security is on, the table's size, and PostgreSQL's row estimate. Every member can open it, viewers included. It is read-only.

The dashboard gets this from the stack's postgres-meta service through the API gateway at /pg/, the route the standard self-hosted configuration already has. It uses the service role key saved on the Settings tab, and the key stays on the server. The same address rules and timeouts as the health check apply.

When the structure can't be read, the page says why: no service role key saved, the key was refused, the gateway has no /pg/ route, postgres-meta returned an error, or the stack couldn't be reached.

Upgrading from 0.1.0-dev.2

Nothing to do beyond pulling the new image. There are no new migrations or configuration settings.

Known limitations

  • Table rows can't be viewed yet. Views, foreign tables, and foreign key details aren't shown either.
  • A schema shows at most 1000 tables and a project at most 500 schemas. The page says when a list was cut short.
  • Schemas with a comma in their name can't be opened, because postgres-meta reads its schema filter as a comma-separated list.
  • Row counts are PostgreSQL's estimates and can be out of date, especially for small or newly loaded tables.
  • Only the Kong gateway is tested. Stacks behind a private certificate authority still can't be reached.

Install

Container image (linux/amd64, linux/arm64):

docker pull ghcr.io/filipnone/supabase-dashboard:0.1.0-dev.3

To deploy on a Linux server with Docker, download supabase-dashboard-0.1.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.