From cfa93a2aa4321a5b407005b83e257d2637caa1d3 Mon Sep 17 00:00:00 2001 From: RamonTC Date: Wed, 13 Sep 2017 13:32:28 +0200 Subject: [PATCH] Updated 11. Setting the solution up in Service Fabric (markdown) --- ...etting-the-solution-up-in-Service-Fabric.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/11.-Setting-the-solution-up-in-Service-Fabric.md b/11.-Setting-the-solution-up-in-Service-Fabric.md index a5df593..de49a91 100644 --- a/11.-Setting-the-solution-up-in-Service-Fabric.md +++ b/11.-Setting-the-solution-up-in-Service-Fabric.md @@ -5,7 +5,7 @@ The ARM script will generate all the necessary Azure resources to publish eShopO Once the SF resources have been successfully created, the next step is to publish the SF projects. These projects are under the directory [SF Directory](https://github.com/dotnet-architecture/eShopOnContainers/tree/eShopOnServiceFabric-Win/ServiceFabric) and contains all the xml config files needed to configure and publish eShopOnContainers. SF is composed by 4 SF apps: - + - eShopOnServiceFabric: contains all the api services consumed by eShop. - eShopOnServiceFabricIdSrv: contains the Identity server for authentication. @@ -15,26 +15,26 @@ Once the SF resources have been successfully created, the next step is to publis Before deploying, replace **ALL** the external urls in the cloud.xml config file of each SF app which reference the SF dns name with the dns name of your SF. Example: - + - + - + - + To deploy the SF apps, open the eShopOnContainers-ServicesAndWebApps.sln with vs2017 (Service Fabric SDK installation must be installed) and right-click on each SF project selecting the publish button. - + A new window will be prompted allowing you to select the SF cluster you have previously created. - + Open the SF explorer page to check out the deployment and healthcheck status. - + - + ### - Deploying eShopOncontainers as Linux Containers to Azure Service Fabric (TBD) \ No newline at end of file