You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our current migrations create minimal data for development which has let us push broken code to prod more than once. Would be great to have better seed data for development (especially a resume field)
The text was updated successfully, but these errors were encountered:
I think the seeding should be entirely separated from the migrations. It was an oversight of mine when setting up the migrations to contain it, as we don't want the seed information to get into the production.
Maybe it would be worth re-titling this issue to be "Set-up Separate Seed System"
Our current migrations create minimal data for development which has let us push broken code to prod more than once. Would be great to have better seed data for development (especially a resume field)
The text was updated successfully, but these errors were encountered: