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.

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

Improved Seeding #134

Closed
Brend-Smits opened this issue May 20, 2020 · 0 comments · Fixed by #135
Closed

Improved Seeding #134

Brend-Smits opened this issue May 20, 2020 · 0 comments · Fixed by #135

Comments

@Brend-Smits
Copy link
Member

Is your feature request related to a problem? Please describe.
Currently the seeding is done in the migrations, it should be moved out of the migrations. The migrations are unreadable at this point and hard to manage.

Describe the solution you'd like
The following things should be seeded in development only:

  • Projects
  • Users
  • Highlighted Projects
  • Embeds
  • Collaborators

The following should be seeded in production only:

  • Roles
  • Single user

I personally recommend doing the seeding in the API project, like it was done in this commit
This way you can easily control what seeding is done in production and what seeding is done in development.

Additional context
This should also fix an issue where the collaborator ID is not unique and causes issues during build time.

@Brend-Smits Brend-Smits added this to In progress in Sprint 4 - Backend May 20, 2020
@wotwot563 wotwot563 moved this from In progress to Review in progress in Sprint 4 - Backend May 21, 2020
Sprint 4 - Backend automation moved this from Review in progress to Done May 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

2 participants