Skip to content

supabase-dashboard 0.1.0-dev.3

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 08 Nov 12:02
· 150 commits to main since this release

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.