From 59c22e03030af69bd83175f7e905ec1bb3f50965 Mon Sep 17 00:00:00 2001 From: Cesar De la Torre Date: Wed, 29 Mar 2017 14:14:42 -0700 Subject: [PATCH] Updated 09. Deploying eShopOnContainers to a "Production" environment (markdown) --- ...ng-eShopOnContainers-to-a-\"Production\"-environment.md" | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git "a/09.-Deploying-eShopOnContainers-to-a-\"Production\"-environment.md" "b/09.-Deploying-eShopOnContainers-to-a-\"Production\"-environment.md" index b54c598..a8a2e61 100644 --- "a/09.-Deploying-eShopOnContainers-to-a-\"Production\"-environment.md" +++ "b/09.-Deploying-eShopOnContainers-to-a-\"Production\"-environment.md" @@ -20,9 +20,11 @@ ESHOP_PROD_EXTERNAL_DNS_NAME_OR_IP=10.121.122.92 **SECOND STEP:** For deploying with docker-compose, instead of doing a regular “docker-compose up” do: **docker-compose -f docker-compose.yml -f docker-compose.prod.yml up -d** + So it uses the docker-compose.**prod**.yml file which uses the EXTERNAL IP or DNS name. https://github.com/dotnet/eShopOnContainers/blob/master/docker-compose.prod.yml -And follow the procedure here: + +And take into account the procedure here: https://github.com/dotnet/eShopOnContainers/wiki/03.-Setting-the-eShopOnContainers-solution-up-in-a-Windows-CLI-environment-(dotnet-CLI,-Docker-CLI-and-VS-Code) -But, +