Removing seeding via prisma #921
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Removed seed command that runs via prisma - Removed all files related to seeding DB via prisma - Created a migration that creates basic Roles needed for app to function - Updated commands in package.json to not include any seeding - Updated docker documentation to remove seeding related lines - Updated Getting started docs to remove seeding related information - Updated .env.example to remove the default values that were used for seeding
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Seeding via prisma was causing lots of different issues both related to docker and normal installs. I have completely removed this and added a DB migration to add the required default roles for the DB to work. No default user is created anymore when setting up the DB.