Edition 0 Updated to asp. Net core 0

}
-
UseLoadTest=${USE_LOADTEST:
-False}
ports:
-
"5110:80"

---

125 
CHAPTER 5 | Designing and Developing Multi-Container and Microservice-Based .NET Applications 
webmvc:
environment:
-
ASPNETCORE_ENVIRONMENT=Development 
-
ASPNETCORE_URLS=http:
//0.0.0.0:80
-
PurchaseUrl=http:
//webshoppingapigw
-
IdentityUrl=http:
//10.0.75.1:5105
-
MarketingUrl=http:
//webmarketingapigw
-
CatalogUrlHC=http:
//catalog-api/hc
-
OrderingUrlHC=http:
//ordering-api/hc
-
IdentityUrlHC=http:
//identity-api/hc
-
BasketUrlHC=http:
//basket-api/hc
-
MarketingUrlHC=http:
//marketing-api/hc
-
PaymentUrlHC=http:
//payment-api/hc
-
SignalrHubUrl=http:
//${ESHOP_EXTERNAL_DNS_NAME_OR_IP}:5202
-
UseCustomizationData=True 
-
ApplicationInsights__InstrumentationKey=$
{
INSTRUMENTATION_KEY
}
-
OrchestratorType=$
{
ORCHESTRATOR_TYPE
}
-
UseLoadTest=${USE_LOADTEST:
-False}
ports:
-
"5100:80"
sqldata:
environment:
-
SA_PASSWORD=
[
PLACEHOLDER
]
-
ACCEPT_EULA=Y 
ports:
-
"5433:1433"
nosqldata:
ports:
-
"27017:27017"
basketdata:
ports:
-
"6379:6379"
rabbitmq:
ports:
-
"15672:15672"
-
"5672:5672"
In this example, the development override configuration exposes some ports to the host, defines 
environment variables with redirect URLs, and specifies connection strings for the development 
environment. These settings are all just for the development environment. 
When you run 
docker-compose up
(or launch it from Visual Studio), the command reads the overrides 
automatically as if it were merging both files. 
Suppose that you want another Compose file for the production environment, with different 
configuration values, ports, or connection strings. You can create another override file, like file named 
docker-compose.prod.yml
with different settings and environment variables. That file might be 
stored in a different Git repo or managed and secured by a different team.