Updated 11. Setting the solution up in Service Fabric (markdown)

RamonTC 2017-10-27 11:06:26 +02:00
parent 20a6a2935f
commit fab78bf0f5

@ -21,7 +21,10 @@ Once the SF resources have been successfully created, the next step is to publis
- 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:
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. Therefore, replace the token **#{your_sf_dns}#** with your cluster DNS name.
Image tags in the servicemanifest.xml files need to be changed as well by replacing the token **#{your_sf_dns}#** with an existing tag (Ex: eshop/ordering.api:**latest**).
Example:
<img src="https://github.com/dotnet-architecture/eShopOnContainers/blob/dev/img/sf/cloud-config.PNG">
@ -85,7 +88,10 @@ Once the SF resources have been successfully created, the next step is to publis
- 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:
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. Therefore, replace the token **#{your_sf_dns}#** with your cluster DNS name.
Image tags in the servicemanifest.xml files need to be changed as well by replacing the token **#{your_sf_dns}#** with an existing tag (Ex: eshop/ordering.api:**latest**).
Example:
<img src="https://github.com/dotnet-architecture/eShopOnContainers/blob/dev/img/sf/cloud-config.PNG">