Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feature: Supabase Studio #68

Closed
1 task done
bdougie opened this issue Jan 6, 2022 · 3 comments · Fixed by #103
Closed
1 task done

Feature: Supabase Studio #68

bdougie opened this issue Jan 6, 2022 · 3 comments · Fixed by #103
Assignees
@0-vortex
Labels
💡 feature released

Comments

@bdougie
Copy link
Member

bdougie commented Jan 6, 2022

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

  • I agree to follow this project's Code of Conduct
@bdougie bdougie mentioned this issue Jan 6, 2022
Merged
15 tasks
@0-vortex
Copy link
Contributor

Can handle the docker and local development parts so will just .take this 🍕

@github-actions
Copy link

Thanks for taking this on! If you have not already, join the conversation in our Discord

@mtfoley mtfoley mentioned this issue Jan 17, 2022
Closed
4 tasks
bdougie added a commit that referenced this issue Jan 22, 2022
@bdougie
feat: adds initial supabase migrations
2f8bdd0 
new users can now clone repo and run supabase studio locally thanks to the local migrations

#68
@bdougie bdougie mentioned this issue Jan 22, 2022
Merged
19 tasks
bdougie added a commit that referenced this issue Jan 24, 2022
@bdougie @0-vortex
feat: Supabase Studio & Local migrations (#103)
fdfd51b 
* 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>
github-actions bot pushed a commit that referenced this issue Jan 24, 2022
@bdougie @open-sauced
chore(minor): release 1.18.0 [skip ci]
a0af3e2 
## [1.18.0](v1.17.0...v1.18.0) (2022-01-24)

### 🍕 Features

* Supabase Studio & Local migrations ([#103](#103)) ([fdfd51b](fdfd51b)), closes [#68](#68) [#104](#104)
@github-actions
Copy link

🎉 This issue has been resolved in version 1.18.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@0-vortex 0-vortex

Labels
💡 feature released
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: Supabase Studio & Local migrations open-sauced/hot
2 participants
@0-vortex @bdougie