Update readme.md
This commit is contained in:
		
							parent
							
								
									ad5b4c5c26
								
							
						
					
					
						commit
						795edefab5
					
				| @ -2,6 +2,7 @@ | |||||||
| 
 | 
 | ||||||
| ## A. Not secured cluster (SF Linux cluster) | ## A. Not secured cluster (SF Linux cluster) | ||||||
| For a secured cluster, see option B. below. | For a secured cluster, see option B. below. | ||||||
|  | 
 | ||||||
| You can always deploy a SF cluster through the Azure portal, as explained in this article: https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-get-started-azure-cluster | You can always deploy a SF cluster through the Azure portal, as explained in this article: https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-get-started-azure-cluster | ||||||
| 
 | 
 | ||||||
| However, when creating a cluster, there are quite a few configurations to take into account, like enabling the internal DNS service or Reverse Proxy service, choosing between Linux/Windows, open/publish your application ports in the load-balancer and most of all (the most complex setup) how to create a secure cluster. | However, when creating a cluster, there are quite a few configurations to take into account, like enabling the internal DNS service or Reverse Proxy service, choosing between Linux/Windows, open/publish your application ports in the load-balancer and most of all (the most complex setup) how to create a secure cluster. | ||||||
| @ -43,6 +44,9 @@ For example, to deploy the cluster to a new resourcegroup located in westus, go | |||||||
| create-resources.cmd servicefabric\LinuxContainers\servicefabricdeploy qa-eshop-sflinux-resgrp -c westus | create-resources.cmd servicefabric\LinuxContainers\servicefabricdeploy qa-eshop-sflinux-resgrp -c westus | ||||||
| ``` | ``` | ||||||
| 
 | 
 | ||||||
|  | You should see a similar execution to the following: | ||||||
|  |  | ||||||
|  | 
 | ||||||
| ## Deploy eShopOnServiceFabric with Visual Studio. | ## Deploy eShopOnServiceFabric with Visual Studio. | ||||||
| 
 | 
 | ||||||
| Alternatively, instead of using ARM templates, you can deploy eShop on service fabric directly by publishing the project eShopOnServiceFabric in eShopOnContainers-ServicesAndWebApps.sln with Visual Studio publish tool. | Alternatively, instead of using ARM templates, you can deploy eShop on service fabric directly by publishing the project eShopOnServiceFabric in eShopOnContainers-ServicesAndWebApps.sln with Visual Studio publish tool. | ||||||
|  | |||||||
		Loading…
	
	
			
			x
			
			
		
	
		Reference in New Issue
	
	Block a user