ayan.poddar/eShopOnContainers
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update readme.md

Browse Source
This commit is contained in:
Cesar De la Torre 2017-10-16 14:38:54 -07:00 committed by GitHub
parent d79e7e2dac
commit c16b1120a0
1 changed files with 17 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
deploy/az/servicefabric/WindowsContainers/readme.md
View File

@ -12,26 +12,33 @@ Within eShopOnContainers root folder, at the folder [..\deploy\az\servicefabric\
Edit the following params in `servicefabricdeploy.parameters.json` file to set your values: Edit the following params in `servicefabricdeploy.parameters.json` file to set your values:
- clusterName: Name of your SF cluster - clusterName: Name of your SF cluster
- clusterLocation: Datacenter location, like westus or westeurope
- computeLocation: Datacenter location, like westus or westeurope
- adminUserName: user-name for VMs administration
- adminPassword: user-password for VMs administration
- dnsName: Name assigned to your SF dns - dnsName: Name assigned to your SF dns
- adminUserName: user name for administration
- adminPassword: user password for administration
Optionally, you can modify which ports are opened in the LoadBalancer for accessing externally to the apps: Optionally, you could modify which ports are opened in the LoadBalancer for the multiple eShopOnContainer apps and API services.
By default, they are setup as:
- webMvcHttpPort: port externally exposed for the WebMVC app - webMvcHttpPort: 5100
- webSpaHttpPort: port externally exposed for the WebSPA app - webSpaHttpPort: 5104
- webStatusHttpPort: port externally exposed for the WebStatus app - webStatusHttpPort: 5107
- IdSrvHttpRule: port externally exposed for the Identity app - IdSrvHttpRule: 5105
- BasketApiHttpRule: 5103
- CatalogApiHttpRule: 5101
- OrderingApiHttpRule: 5102
- MarketingApiHttpRule: 5110
- LocationsApiHttpRule: 5109
## Deploy the template ## Deploy the template
Once parameter file is edited you can deploy it using [create-resources script](../readme.md). Once parameter file is edited you can deploy it using [create-resources script](../readme.md).
i. e. if you are in windows, to deploy sql databases in a new resourcegroup located in westus, go to `deploy\az` folder and type: For example, to deploy the cluster to a new resourcegroup located in westus, go to `deploy\az` folder and type:
``` ```
create-resources.cmd servicefabric\WindowsContainers\servicefabricdeploy newResourceGroup -c westus create-resources.cmd servicefabric\WindowsContainers\servicefabricdeploy newResourceGroup -c westus
``` ```
## 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.