kemal.earthandJoshen Lim
1bb9453b0c
* feat: tidy up query perf column headers * feat: update col widths and which ones are sortable This gives a reasonable column width to all cols as well as adds an option for us to filter out which columns we dont want to make the table sortable by. * feat: column order and word wrapping for query * feat: column data text align for numbers * fix: pointer event was preventing index advisor icon popover * feat: use code block instead of editor Swapped Editor out for Code block as its less expensive and modified it to add pgsql syntax highlighting * fix: small truncation issue * chore: remove unused sort function * fix: sort menu closing on first click Sort menu of a column no longer disappears on first click * feat: move sorting and ordering over to nuqs This removes the usage of Next Router params and uses Nuqs instead for managing the QP table sorting and ordering. * feat: add clear sorting button to filter bar * chore: remove unused files * fix: add highlighting for selected sort * Nit update sort * nit: smol styling update for direction * feat: inian feedback on time based numbers * fix: return number instead of string for total time We were returning a string for total time percentage which meant the sorting was a little bit off * Shift roles to nuqs * chore: clean up * fix: smaller viewport filter bar --------- Co-authored-by: Joshen Lim <joshenlimek@gmail.com>
Supabase Studio
A dashboard for managing your self-hosted Supabase project, and used on our hosted platform. Built with:
What's included
Studio is designed to work with existing deployments - either the local hosted, docker setup, or our CLI. It is not intended for managing the deployment and administration of projects - that's out of scope.
As such, the features exposed on Studio for existing deployments are limited to those which manage your database:
- Table & SQL editors
- Saved queries are unavailable
- Database management
- Policies, roles, extensions, replication
- API documentation
Managing Project Settings
Project settings are managed outside of the Dashboard. If you use docker compose, you should manage the settings in your docker-compose file. If you're deploying Supabase to your own cloud, you should store your secrets and env vars in a vault or secrets manager.
How to contribute?
- Branch from
masterand name your branches with the following structure{type}/{branch_name}- Type:
chore | fix | feature - The branch name is arbitrary — just make sure it summarizes the work.
- Type:
- When you send a PR to
master, it will automatically tag members of the frontend team for review. - Review the contributing checklists to help test your feature before sending a PR.
- The Dashboard is under active development. You should run
git pullfrequently to make sure you're up to date.
Developer Quickstart
Note
Supabase internal use: To develop on Studio locally with the backend services, see the instructions in the internal
infrastructurerepo.
# You'll need to be on Node v20
# in /studio
npm i # install dependencies
npm run dev:secrets:pull # Supabase internal use: if you are working on the platform version of the Studio
npm run dev # start dev server
npm run test # run tests
npm run -- --watch # run tests in watch mode
Running within a self-hosted environment
Follow the self-hosting guide to get started.
cd ..
cd docker
docker compose -f docker-compose.yml -f ./dev/docker-compose.dev.yml up
Once you've got that set up, update .env in the studio folder with the corresponding values.
POSTGRES_PASSWORD=
SUPABASE_ANON_KEY=
SUPABASE_SERVICE_KEY=
Then run the following commands to install dependencies and start the dashboard.
npm install
npm run dev
If you would like to configure different defaults for "Default Organization" and "Default Project", you will need to update the .env in the studio folder with the corresponding values.
DEFAULT_ORGANIZATION_NAME=
DEFAULT_PROJECT_NAME=