* lw13:d4 * www queues page (#30907) * new products menu * set up cron page * set up cron page * placeholder sections * set up queues page * update meta * update Supabase Queues landing page content * Updated the text to exclude queue creation/management from the API management section * queues www page --------- Co-authored-by: Wen Bo Xie <wenbo.xie3@gmail.com> Co-authored-by: Greg Papas <gregpapas@Gregs-MacBook-Pro.local> * feat: add queue module (#30853) * feat: postgres integrations Create a new global navigation and homepage menu section for the Postgres Integrations category. reorg: move cron docs into postgres integrations feat: postgres integrations Create a new global navigation and homepage menu section for the Postgres Integrations category. reorg: move cron docs into postgres integrations docs homepage layout feat: postgres integrations Create a new global navigation and homepage menu section for the Postgres Integrations category. reorg: move cron docs into postgres integrations feat: postgres integrations Create a new global navigation and homepage menu section for the Postgres Integrations category. reorg: move cron docs into postgres integrations docs homepage layout feat: postgres integrations Create a new global navigation and homepage menu section for the Postgres Integrations category. reorg: move cron docs into postgres integrations feat: postgres integrations Create a new global navigation and homepage menu section for the Postgres Integrations category. reorg: move cron docs into postgres integrations docs homepage layout * fix: add pg_cron back to extensions sidebar * update Supabase Cron docs * feat: add queues module feat: add queues module * remove staging url from screenshots * remove outdated cron files * typo * queues description update --------- Co-authored-by: Francesco Sansalvadore <f.sansalvadore@gmail.com> Co-authored-by: Wen Bo Xie <wenbo.xie3@gmail.com> Co-authored-by: Oliver Rice <github@oliverrice.com> * visibility timeout to window * queues landing page sql example * capitalize Dashboard * cron blog post citus data callout update * added draft of queues feature * updated features bulleting * pluralize queues * fix Queues features page * Inital bp * queues docs updates * format queues docs * queues blog post updates * edits * Update the images for role in the docs quickstart for queues. * updated images * update images * update more images * Update 2024-12-05-supabase-queues.mdx * fix breaks * punchier title * better ul * clean up * Retake screenshots * grammar * whitelines * video + images * update docs * blog updates * blog update * api snippet * api snippet fix * queues features yt video * api snippet fix * update docs * blog update * api snippet fix and vale * format * vale off * vale off * blog update --------- Co-authored-by: Francesco Sansalvadore <f.sansalvadore@gmail.com> Co-authored-by: Greg Papas <gregpapas@Gregs-MacBook-Pro.local> Co-authored-by: Charis <26616127+charislam@users.noreply.github.com> Co-authored-by: Oliver Rice <github@oliverrice.com> Co-authored-by: Terry Sutton <saltcod@gmail.com> Co-authored-by: Copple <10214025+kiwicopple@users.noreply.github.com> Co-authored-by: Ivan Vasilov <vasilov.ivan@gmail.com> Co-authored-by: Jonathan Summers-Muir <MildTomato@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=