From f2f1934940286f227e4bcf8ff55b466a31ff3d42 Mon Sep 17 00:00:00 2001
From: asziranyi <asziranyi@gmail.com>
Date: Thu, 17 Nov 2016 15:50:47 +0100
Subject: [PATCH 1/3] add vagrant-vbguest installation link

---
 prepare-local/README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/prepare-local/README.md b/prepare-local/README.md
index ff4d3fb9..010b2462 100644
--- a/prepare-local/README.md
+++ b/prepare-local/README.md
@@ -13,6 +13,7 @@ Virtualbox, Vagrant and Ansible
 - Virtualbox: https://www.virtualbox.org/wiki/Downloads
 
 - Vagrant: https://www.vagrantup.com/downloads.html
+  - install vagrant-vbguest plugin (https://github.com/dotless-de/vagrant-vbguest)
 
 - Ansible:
   - install Ansible's prerequisites:

From 6cd8c32621d8c2f3b51a5968861a2bec142f26ac Mon Sep 17 00:00:00 2001
From: Drew Moseley <drew@moseleynet.net>
Date: Thu, 17 Nov 2016 12:07:42 -0500
Subject: [PATCH 2/3] Install pycrypto

Not sure if it's somehow unique to my setup but Ansible needed me to install pycrypto as well.
---
 prepare-local/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/prepare-local/README.md b/prepare-local/README.md
index ff4d3fb9..2a3a1f7e 100644
--- a/prepare-local/README.md
+++ b/prepare-local/README.md
@@ -17,7 +17,7 @@ Virtualbox, Vagrant and Ansible
 - Ansible:
   - install Ansible's prerequisites:
 
-          $ sudo pip install paramiko PyYAML Jinja2 httplib2 six
+          $ sudo pip install paramiko PyYAML Jinja2 httplib2 six pycrypto
 
   - clone the Ansible repository and checkout to a stable version
     (don't forget the `--recursive` argument when cloning!):

From e16e23e2bda208a0de16a02b762250f591a924c9 Mon Sep 17 00:00:00 2001
From: Jerome Petazzoni <jerome.petazzoni@gmail.com>
Date: Fri, 18 Nov 2016 10:06:10 -0800
Subject: [PATCH 3/3] Add supergrok instructions

---
 README.md | 25 +++++++++++++------------
 1 file changed, 13 insertions(+), 12 deletions(-)

diff --git a/README.md b/README.md
index ba0c4122..4ada1a07 100644
--- a/README.md
+++ b/README.md
@@ -46,19 +46,20 @@ The nodes are not directly reachable from outside; so when the slides tell
 you to "connect to the IP address of your node on port XYZ" you will have
 to use a different method.
 
-We suggest to use ngrok. When you need to expose, say, port 8000 on one of
-your nodes, just follow these instructions:
+We suggest to use "supergrok", a container offering a NGINX+ngrok combo to
+expose your services. To use it, just start (on any of your nodes) the
+`jpetazzo/supergrok` image. The image will output further instructions:
 
-- on that node, run `docker run --net host -ti jpetazzo/ngrok http 8000`
-- you should see the ngrok CLI
-- when it says "Tunnel Status: online", you're set!
-- browse to http://????????.ngrok.io, it will route to port 8000
-- you can stop ngrok with Ctrl-C
-- if you want to keep ngrok runing in the background, we recommend
-  that you use `tmux`
-- NOTE: there might be a bug right now with play-with-docker and
-  Ctrl-P Ctrl-Q, so we don't recommend that you try to detach from
-  the ngrok container! Sorry...
+```
+docker run --name supergrok -d jpetazzo/supergrok
+docker logs --follow supergrok
+```
+
+The logs of the container will give you a tunnel address and explain you
+how to connected to exposed services. That's all you need to do!
+
+We are also working on a native proxy, embedded to Play-With-Docker.
+Stay tuned!
 
 <!--