This repository has been archived by the owner on Sep 26, 2024. It is now read-only.
Feature: Supabase Studio #68
Comments
|
Can handle the docker and local development parts so will just |
|
Thanks for taking this on! If you have not already, join the conversation in our Discord |
bdougie
added a commit
that referenced
this issue
Jan 22, 2022
new users can now clone repo and run supabase studio locally thanks to the local migrations #68
19 tasks
bdougie
added a commit
that referenced
this issue
Jan 24, 2022
* successful dump * feat: adds initial supabase migrations new users can now clone repo and run supabase studio locally thanks to the local migrations #68 * perf: minimally extend supabase studio feature (#104) * refactor: remove unneeded data dump * refactor: split migrations apart * perf: add minor migration improvements * quick spelling Co-authored-by: Brian Douglas <bdougie@users.noreply.github.com> * adds supabase studio notes * Update README.md Co-authored-by: TED Vortex (Teodor-Eugen Duțulescu) <237133+0-vortex@users.noreply.github.com>
|
🎉 This issue has been resolved in version 1.18.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Type of feature
Feature
Current behavior
At the moment the only person that contributes to any database changes is @bdougie. While getting the project off the ground is fine, but this will be a limitation for future contributors as the site grows to be more complicated.
Desired solution
Connect the database to a local studio instance that folks run locally. This will require some sort RLS and user management which is still actively being worked on in #20
If anyone has Supabase experience, feel free to comment here or in the discord.
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: