From 27c8abc3e769c388418d1116bc509358cb124480 Mon Sep 17 00:00:00 2001 From: RamonTC Date: Tue, 10 Oct 2017 19:39:19 +0200 Subject: [PATCH] Updated 11. Setting the solution up in Service Fabric (markdown) --- 11.-Setting-the-solution-up-in-Service-Fabric.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/11.-Setting-the-solution-up-in-Service-Fabric.md b/11.-Setting-the-solution-up-in-Service-Fabric.md index 4b0a017..6271281 100644 --- a/11.-Setting-the-solution-up-in-Service-Fabric.md +++ b/11.-Setting-the-solution-up-in-Service-Fabric.md @@ -3,7 +3,7 @@ In order to deploy eShopOnContainers as Windows Containers an Azure SF environment must be first set. There is available an ARM template to do that job in the following link [SF Win ARM deployment](https://github.com/dotnet-architecture/eShopOnContainers/tree/dev/deploy/az/servicefabric/WindowsContainers). Follow the steps in [create SF](https://github.com/dotnet-architecture/eShopOnContainers/blob/dev/deploy/az/servicefabric/WindowsContainers/readme.md). The ARM script will generate all the necessary Azure resources to publish eShopOnContainers as windows containers. -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/dev/ServiceFabric) and contains all the xml config files needed to configure and publish eShopOnContainers. SF is composed by 4 SF apps: +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/dev/ServiceFabric/Windows) and contains all the xml config files needed to configure and publish eShopOnContainers. It is composed by the following SF projects: @@ -12,6 +12,10 @@ Once the SF resources have been successfully created, the next step is to publis - eShopOnServiceFabricWebMVC: contains the MVC web app. - eShopOnServiceFabricWebSPA: containes the SPA web app. - eShopOnServiceFabricWebStatus: contains the web app for service health checking. +- eShopOnServiceFabricBus: contains a bus service (Rabbitmq). +- eShopOnServiceFabricNoSql: contains a no sql service (MongoDB). +- eShopOnServiceFabricRedis: contains a cache service (Redis). +- eShopOnServiceFabricSql: contains a sql service (Mssql). 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: @@ -23,7 +27,10 @@ Before deploying, replace **ALL** the external urls in the cloud.xml config file -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. +To deploy the SF apps: +- Open the eShopOnContainers-ServicesAndWebApps.sln with vs2017 (Service Fabric SDK installation must be installed). +- Add the existing SF projects in the solution in order to be published. +- Right-click on each SF project selecting the publish button. Firstly, publish the infrastructure services [SF infrastructure services](https://github.com/dotnet-architecture/eShopOnContainers/tree/dev/ServiceFabric/Windows/Infrastructure) and once deployed, do the same process for the rest of apps.