supabase icon indicating copy to clipboard operation
supabase copied to clipboard

Provide seed data for individual testing/development

Open pascalwengerter opened this issue 1 year ago • 4 comments

Is your feature request related to a problem? Please describe.

While working on #409 I had to create and configure my Supabase database manually. Knowing there is a possibility to dump (and upload?) existing databases, I'd love to have a quickstart feature where one can seed a fresh database. Saying that, I'm aware that the OAuth setup can't be automated so there'll always be some degree of manual work.

Describe the solution you'd like

A data dump within the repo and 1-2 simple commands or instructions on how to use it

Describe alternatives you've considered

Doing it manually isn't the biggest pain ever, but it would shave a couple of minutes off of potential contributor's necessary time commitment

pascalwengerter avatar Sep 01 '24 04:09 pascalwengerter

There is a way of doing it described in the official Supabase Local Dev Docs

In essence, you configure the config.toml file, add a couple of sql files in seeds subdirectory and/or some assets for buckets - all within the supabase directory.

For reference, you can check out my implementation here: https://github.com/Nagell/portfolio-nuxt/tree/main/supabase

Hope it helps in your case.

I believe this ticket can be closed, although a tip in the plugin docs on where to find the official "Local Dev documentation" could be very helpful.

Nagell avatar Jan 04 '25 14:01 Nagell

There is a way of doing it described in the official Supabase Local Dev Docs

In essence, you configure the config.toml file, add a couple of sql files in seeds subdirectory and/or some assets for buckets - all within the supabase directory.

For reference, you can check out my implementation here: https://github.com/Nagell/portfolio-nuxt/tree/main/supabase

Hope it helps in your case.

I believe this ticket can be closed, although a tip in the plugin docs on where to find the official "Local Dev documentation" could be very helpful.

@Nagell thanks for the pointers! Why close the ticket without having seeds in the repository, though?

pascalwengerter avatar Jan 15 '25 19:01 pascalwengerter

@pascalwengerter ahh nvm, ignore the last sentence please. I just oversaw the fact that you are working on some ticket in this repo. I assumed that you can create such seed files and commit them, but it seems not to be the case.

Nagell avatar Jan 15 '25 21:01 Nagell

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

github-actions[bot] avatar May 06 '25 13:05 github-actions[bot]