From be661185146533dc7a37055e804d5d3989851402 Mon Sep 17 00:00:00 2001
From: Michiel de Jong <michiel@unhosted.org>
Date: Tue, 18 Nov 2014 14:11:53 +0000
Subject: [PATCH] mention Dockerfiles issue 39 in the reference manual

---
 doc/deploying-a-server.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/doc/deploying-a-server.md b/doc/deploying-a-server.md
index 3b1fbc8..4456338 100644
--- a/doc/deploying-a-server.md
+++ b/doc/deploying-a-server.md
@@ -38,7 +38,9 @@ Make sure you read [getting started](getting-started-as-a-hoster.md) first.
   * Rewrite the haproxy configuration
   * (Re)start haproxy
 
-* If the domain runs wordpress, then the git clone from backup will fail because of [issue 46](https://github.com/indiehosters/indiehosters/issues/46), so make sure to follow the workaround steps from there.
+* If the domain runs wordpress, then:
+  * the git clone from backup will fail because of [issue 46](https://github.com/indiehosters/indiehosters/issues/46), so make sure to follow the workaround steps from there.
+  * initial wordpress setup will be impossible with the redirect because of [Dockerfiles issue 39](https://github.com/indiehosters/dockerfiles/issues/39), so make sure to follow the workaround steps from there.
 
 ### Adding a new website to your server
 * For each site you want to deploy on the server, e.g. example.com, do the following:
-- 
GitLab