From 75ec58db3a48147b0be83417d47972a3a5244771 Mon Sep 17 00:00:00 2001
From: earcanal <paul@miraclefish.com>
Date: Fri, 28 Sep 2018 11:05:52 +0100
Subject: [PATCH] Update 1-generate-https.md

Instructions for > 1 (SSL) container per droplet.
---
 pages/1-generate-https.md | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/pages/1-generate-https.md b/pages/1-generate-https.md
index 688908d..c12825a 100644
--- a/pages/1-generate-https.md
+++ b/pages/1-generate-https.md
@@ -388,3 +388,20 @@ Now that your container is running, you can refer to the [previous page](/genera
     <a href="/generate"><button class="previous-button btn btn-primary"><i class="fa fa-chevron-left"></i> </button></a>
     <a href="/customize"><button class="next-button btn btn-primary"><i class="fa fa-chevron-right"></i> </button></a>
 </div><br>
+
+**One droplet, multiple containers**
+
+To take things one step further, you might want to simultaneously run multiple studies (SSL containers) on the same droplet. This saves you the effort and cost of having one container per droplet. You can do this by mapping additional containers to ports other than the standard 80 (HTTP) and 443 (HTTPS) on the droplet.  To try this out, build a container containing `test-task`.
+
+```
+docker run -v $PWD:/data vanessa/expfactory-builder build test-task --input build/docker/Dockerfile.https
+docker build --no-cache -t expfactory/experiments .
+ ```
+ 
+Run this container as follows:
+ 
+```
+$ docker run -p 8000:80 -p 4443:443 -v /etc/ssl/certs:/etc/ssl/certs:ro -v /etc/ssl/private:/etc/ssl/private:ro -v /tmp/test-experiment/data:/scif/data expfactory/experiments start
+```
+
+You can then access this droplet at `https://your.domain:4443/`.