Committing work for creating docker images of Web and API apps
Outstanding work include: - Adding CI/CD workflow compatible with Woodpecker CI - Figure out how to load runtime environment variables onto the API docker build process
This commit is contained in:
24
Readme.md
24
Readme.md
@ -1,23 +1,7 @@
|
||||
# YABA: Yet Another Bookmark App
|
||||
|
||||
## Developer Guides
|
||||
## Developer Guide
|
||||
|
||||
### Running Migrations
|
||||
When running migrations, .NET seems to be ignoring dependency injection settings. In order to get around this, be sure to add the connection string to the command like. For example, when adding the migration:
|
||||
|
||||
```
|
||||
dotnet ef migrations add InitialMigration -p YABA.Data -s YABA.API --context YABABaseContext -- {CONNECTION_STRING_HERE}
|
||||
```
|
||||
|
||||
When removing last migration:
|
||||
```
|
||||
dotnet ef migrations remove InitialMigration -p YABA.Data -s YABA.API --context YABABaseContext -- {CONNECTION_STRING_HERE}
|
||||
```
|
||||
|
||||
When applying migrations:
|
||||
```
|
||||
dotnet ef database update -p YABA.Data -s YABA.API -c YABABaseContext -- { CONNECTION_STRING_HERE }
|
||||
```
|
||||
|
||||
As per the documentation [on MSDN](https://learn.microsoft.com/en-ca/ef/core/cli/dbcontext-creation?tabs=dotnet-core-cli#from-application-services):
|
||||
> The -- token directs dotnet ef to treat everything that follows as an argument and not try to parse them as options. Any extra arguments not used by dotnet ef are forwarded to the app.
|
||||
The application is divided into two parts. Refer to the Readme on the root of the following sections for more information:
|
||||
- API: [Readme](API/Readme.md)
|
||||
- Web: [Readme](Web/Readme.md)
|
||||
Reference in New Issue
Block a user