From 3ac68e127138abdf5ff7f4a1edb3a1cc0f8e5c60 Mon Sep 17 00:00:00 2001 From: Yegor Date: Wed, 17 Jul 2019 02:08:54 +0300 Subject: [PATCH] Fixed typo and added port number (#8850) * Fixed typo and added port number Lost couple minutes figuring out on which port is app running on vm-s. So I think it would be nice to add port number in description or change picture a little. * Update part4.md standardizing formatting --- get-started/part4.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/get-started/part4.md b/get-started/part4.md index a265960b6d..2431f20456 100644 --- a/get-started/part4.md +++ b/get-started/part4.md @@ -338,7 +338,7 @@ myvm2 - hyperv Running tcp://192.168.200.181:2376 v17.06. Now that you have `myvm1`, you can use its powers as a swarm manager to deploy your app by using the same `docker stack deploy` command you used in part -3 to `myvm1`, and your local copy of `docker-compose.yml.`. This command may take a few seconds +3 to `myvm1`, and your local copy of `docker-compose.yml`. This command may take a few seconds to complete and the deployment takes some time to be available. Use the `docker service ps ` command on a swarm manager to verify that all services have been redeployed. @@ -415,7 +415,7 @@ You can access your app from the IP address of **either** `myvm1` or `myvm2`. The network you created is shared between them and load-balancing. Run `docker-machine ls` to get your VMs' IP addresses and visit either of them on a -browser, hitting refresh (or just `curl` them). +browser on port 4000, hitting refresh (or just `curl` them). ![Hello World in browser](images/app-in-browser-swarm.png)