From fa27c959e2c06191802173429271db6b9789295d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Eduard=20Tom=C3=A0s?= Date: Wed, 6 Sep 2017 07:20:20 +0200 Subject: [PATCH] Updated 08. Setting up and Deploying eShopOnContainers to Windows Containers (markdown) --- ...-up-and-Deploying-eShopOnContainers-to-Windows-Containers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/08.-Setting-up-and-Deploying-eShopOnContainers-to-Windows-Containers.md b/08.-Setting-up-and-Deploying-eShopOnContainers-to-Windows-Containers.md index 2a87c59..908e6dc 100644 --- a/08.-Setting-up-and-Deploying-eShopOnContainers-to-Windows-Containers.md +++ b/08.-Setting-up-and-Deploying-eShopOnContainers-to-Windows-Containers.md @@ -58,7 +58,7 @@ If you use `start-windows-containers.ps1` script to launch the containers or inc **Note**: Read this only if you use any other RabbitMQ image (or server) that have its own user/password needed. -We support any user/password needed using the environment variables `ESHOP_SERVICE_BUS_USERNAME` and `ESHOP_SERVICE_BUS_PASSWORD. These variables are used to set a username and password when connecting to RabbitMQ. So: +We support any user/password needed using the environment variables `ESHOP_SERVICE_BUS_USERNAME` and `ESHOP_SERVICE_BUS_PASSWORD`. These variables are used to set a username and password when connecting to RabbitMQ. So: * In Linux these variables can be unset (or empty) * In Windows these variables should be set