👷♂️ 306 move seed data and migrations out of api #309
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
danielmackay
requested review from
wicksipedia,
GordonBeeming,
Hona and
william-liebenberg
matt-goldman-ssw
approved these changes
May 21, 2024
danielmackay
requested review from
matt-goldman-ssw,
Hona,
wicksipedia,
william-liebenberg and
matt-goldman
and removed request for
wicksipedia,
GordonBeeming,
Hona,
william-liebenberg and
matt-goldman-ssw
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.
✏️ #294
✏️ Previously DB creation and data seeding was done in
Program.csin Development mode. There is risk that this might be run on PROD which isn't great.PMigrated DB migrations and seeding to a new project under
Tools\Database. This project is then called byup.ps1to handle creation of SQL Server, DB, and Seed data all in one command.✏️ Yes with @william-liebenberg