Skip to content

Commit 2d13a06

Browse files
committed
type fix and enhancement
Added extra information and type fixes
1 parent d5f44ff commit 2d13a06

File tree

4 files changed

+14
-2
lines changed

4 files changed

+14
-2
lines changed

docs/en/Development-Mvc-Core-Docker.md

Lines changed: 14 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -42,11 +42,23 @@ Below you can see **docker-compose-mvc-only** running:
4242
There are three docker solutions you can set as startup project to run;
4343

4444
1. **docker-compose-all:** Runs Web.Host, Web.MVC and Web.Public projects together.
45-
2. **docker-compose-host-only:** Run only Web.Host project.
45+
2. **docker-compose-host-only:** Runs only Web.Host project.
4646
3. **docker-compose-mvc-only:** Runs only Web.MVC project.
4747

4848
Each docker-compose files have override.yml files to set the other environments like certification informations, docker volumes or AspnetCore Environment.
4949

50+
<img src="images/development-docker-mvc/docker-override-configuration.png" alt="docker-override-configuration" style="zoom:100%;" />
51+
5052
Configuration is separated between **docker development** and default **IIS development**.
5153

52-
If you want to change the default connection string when running on containers; you need to change the environment variable **ConnectionStrings__Default** in corresponding **docker-compose.yml** file since it overrides the connection string set it appsettings.json. This way you can use both development environments without mixing up the configurations.
54+
If you want to change the default connection string when running on containers; you need to change the environment variable **ConnectionStrings__Default** in corresponding **docker-compose.yml** shown below:
55+
56+
<img src="images/development-docker-mvc/docker-cs-configuration.png" alt="docker-cs-configuration" style="zoom:100%;" />
57+
58+
This environment variable overrides the connection string which has been set it appsettings.json. This way you can use both development environments without mixing up the configurations.
59+
60+
In some cases, you may get **container conflict errors** when switching between docker projects; like debugging **docker-compose-mvc-only** first then start debugging **docker-compose-all** after stopping the first one.
61+
62+
<img src="images/development-docker-mvc/docker-container-conflict.png" alt="docker-cs-configuration" style="zoom:100%;" />
63+
64+
This occurs because the mvc container is still alive even if you stop debugging. To avoid container conflicts, you need to **Clean** the solution (right click to docker project and clean option) to remove the container completely before running the **docker-compose-all** which uses common containers.
Loading
Loading
Loading

0 commit comments

Comments
 (0)