Repository navigation
Seed with a Script #66
Description
Feature request
Is your feature request related to a problem? Please describe.
We currently have seeding scripts written in TypeScript.
They served two purposes:
- Reproducibility of the project: if we had to deploy somewhere else, we would still have the essential data needed for the app to work.
- Easily provision a local development environment.
There is currently no way to run such seeding scripts after running supabase start since the CLI is blocking, which means we can't simply add a dev:start script to run supabase start && yarn db:seed.
Describe the solution you'd like
- We would like
supabase startto accept a flag to run a custom seeding command. - We would like to have the possibility to edit the Supabase config to run a seeding script
Describe alternatives you've considered
We considered converting our seeding scripts to SQL, but I believe this is a feature that could benefit Supabase too.
Additional context
The data we want to seed is pretty static.
We wrote our seeding scripts in TypeScript.
We could also solve our problem with #30.
Reacted by Brandon (opti), Vinzent, Mads, Haydn Ewers, dmatthams, Felipe Palazzo, Alpha Intelligence and Oliver Barnwell
Activity
madeleineostoja commentedon Oct 8, 2022
This would be awesome for seeding local storage with the supabase API as well, rather than running a custom command with a node script for doing that after seeding.
sweatybridge commentedon Oct 14, 2022
Hello, since
supabase startis no longer blocking, the suggested script in this ticketsupabase start && yarn db:seedshould work now.The more general request for running custom command after supabase start is similar to hooks. We have a proposal in #501 on how this might be done. Please have a look there and comment on anything you'd like to add.
Appreciate your feedback.