From 017be6879e093ea3309dd9e470b0d605aa6ba897 Mon Sep 17 00:00:00 2001
From: Pierre Ozoux <pierre@ozoux.net>
Date: Fri, 6 Jan 2017 12:35:20 +0000
Subject: [PATCH] Update with lb_web network, fixes #6

---
 README.md | 14 ++++++++++++--
 1 file changed, 12 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index a49babc..9aba6cb 100644
--- a/README.md
+++ b/README.md
@@ -22,17 +22,27 @@ Each time you add a container with the environment variable `VIRTUAL_HOST` it wi
 ## Get started
 
 ```
+docker network create lb_web
 git clone https://github.com/indiehosters/haproxy.git
 cd haproxy
 docker-compose up -d
 ```
 
-And profit!
+In these commands, we just created one network (lb_web) to isolate HAProxy with the web servers, and then, we started the containers of HAProxy and companions.
 
 ```
-docker run -e VIRTUAL_HOST=example.org nginx
+docker run --network=lb_web -e VIRTUAL_HOST=example.org nginx
 ```
 
+Here, we just started the most simple web server, and added to the lb_web network.
+The only thing that HAProxy needs to see and connect to this container are the following:
+ - expose a port 80
+ - have a VIRTUAL_HOST variable setup with the domain name
+ - be in the lb_web network
+ 
+And finally for HAProxy to be able to provision the Let's encrypt certificate, you need to configure your DNS for example.org to point to the IP of HAProxy.
+
+
 ## Contributing
 
 If you have any issue (something not working, missing doc), please do report an issue here! Thanks
-- 
GitLab