37f77ae482
* add new ui for restore to new project * rm false * fix typeerr badly * add form with name and new project pass * fix flash in loading > results state change * restore api types * update api types, add pitr picker * add additional monthly spend section * fix loading state jump * update copy * update api types * update to new clone status api res * fix mutation missing vars * dont render logical backups in list * fix state issue on submit * better pitr empty state * Update apps/studio/pages/project/[ref]/database/backups/restore-to-new-project.tsx Co-authored-by: Wen Bo Xie <5532241+w3b6x9@users.noreply.github.com> * Update apps/studio/pages/project/[ref]/database/backups/restore-to-new-project.tsx Co-authored-by: Joshen Lim <joshenlimek@gmail.com> * Apply suggestions from code review Co-authored-by: Joshen Lim <joshenlimek@gmail.com> Co-authored-by: Wen Bo Xie <5532241+w3b6x9@users.noreply.github.com> * update api types to accept recoveryTimeTarget for PITR restores * simplify pitr code a bit cleanup state bugs * cleanup * add PITR submit * dont show restore btn unless status is complete * update api types * fix backups nav * markdown descs and fix type err in nav * check if project is cloned * fix: make source project data optional * fix datepicker highlighted day style * fix tz picker * check if its same or before/after in isWithinRange * update api types fix issue with clones * unsus * fix markdown rendering issues * add badge * Update database roles and permissions description * Update restore message text in PITR form component * Update key attribute to item.id in DatabaseBackupsNav component * Add conditional rendering for multiple available dates * Refactor dialog section styles in restore-to-new-project.tsx * Update null to undefined in conditional text assignment * reuse component in pitr backups * Update apps/studio/pages/project/[ref]/database/backups/restore-to-new-project.tsx Co-authored-by: Wen Bo Xie <5532241+w3b6x9@users.noreply.github.com> * Update link to original project in RestoreToNewProject * fix prettier --------- Co-authored-by: Wen Bo Xie <5532241+w3b6x9@users.noreply.github.com> Co-authored-by: Joshen Lim <joshenlimek@gmail.com> Co-authored-by: Crispy1975 <12525875+Crispy1975@users.noreply.github.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=