Ivan Vasilov
c5bf65b0b4
* Fix childProps in Admonition so that they're added as a prop to the main div. * Replace the admonition with Alert in Wrapper tab page to add a gap between childs. * Add s3 vectors fdw. * Minor fix to FormSection. * Update the fdw mutations to support passing in options. * Refactor the vector flow to create fdws. * Revert cron description change. * If the bucket can't be created, don't create a fdw. * Update/delete the fdw when deleting a table or a bucket. * Minor fixes. * Clean up the delete modal. * Handle edge cases when missing a wrapper. * Remove the admonition in the create bucket modal. * Fix the loading state when creating a bucket. * Fix the createWrapper sheet to work with s3 vectors. * Fix undefined wrapperMeta issue. * Create the schema when installing a wrapper. * Tiny cleanup. * Clean up unneeded useState. Create a wrapper only if the all conditions are met. * Fix all comments. * Add s3 vectors for docs. * Add a link and fix the file name for S3 Vectors in docs. * Hide the table editor button if the wrapper instance is missing. * Small fixes.
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
## For external contributors
pnpm install # install dependencies
pnpm run dev # start dev server
## For internal contributors
## First clone the private supabase/infrastructure repo and follow instructions for setting up mise
mise studio # Run from supabase/infrastructure alongside `mise infra`
## For all
pnpm run test # run tests
pnpm run test -- --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=