From 46b796ba3e9372dfd340dcafd6a560cf379973f1 Mon Sep 17 00:00:00 2001 From: RamonTC Date: Mon, 18 Dec 2017 09:17:28 +0100 Subject: [PATCH] Updated 11. Setting the solution up in Service Fabric (markdown) --- 11.-Setting-the-solution-up-in-Service-Fabric.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/11.-Setting-the-solution-up-in-Service-Fabric.md b/11.-Setting-the-solution-up-in-Service-Fabric.md index 4640b3d..f48581c 100644 --- a/11.-Setting-the-solution-up-in-Service-Fabric.md +++ b/11.-Setting-the-solution-up-in-Service-Fabric.md @@ -22,7 +22,7 @@ Once the SF resources have been successfully created, the next step is to publis - 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. 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**). +Image tags in the servicemanifest.xml files need to be changed as well by replacing the token **#{tag}#** with an existing tag (Ex: eshop/ordering.api:**latest**). Example: