Supabase Studio
A dashboard for managing your self-hosted Supabase project, and used on our hosted platform. Built with:
Disclaimer
Supabase Studio is under heavy development. Apologies for any confusing patterns used while we're refactoring the codebase. If you're planning to contribute, it is advised that you run git pull
frequently to retrieve the latest updates.
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
master
and name your branches with the following structure{type}/{branch_name}
- Type:
chore | fix | feature
- Branch Name: Arbitrary, just make sure it summarizes the work
- Type:
- Send a PR to
master
and tag the following members in your PR as reviewers
Running within a self-hosted environment
Firstly, follow the guide here to get started with self-hosted Supabase.
cd ..
cd docker
docker-compose 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 follow commands to install dependencies and start the dashboard.
from Hacker News https://ift.tt/3I5r6A2
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.