From 703827cea4d75e9ed5c993b671908386d63e6348 Mon Sep 17 00:00:00 2001
From: Michiel de Jong <michiel@unhosted.org>
Date: Tue, 18 Nov 2014 12:00:11 +0000
Subject: [PATCH] mention issue #46 in docs

---
 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 57b119f..91370dd 100644
--- a/doc/deploying-a-server.md
+++ b/doc/deploying-a-server.md
@@ -18,7 +18,7 @@ Make sure you read [getting started](getting-started-as-a-hoster.md) first.
 * Add the ssh key from k3:.ssh/id_rsa.pub to the authorized_keys for the git user (not the root user) on bu25.
 * Check that you can `ssh git@bu25` from k3.
 * Exit from the double ssh back to your laptop, and from the root folder of this repository, run `sh ./deploy/deploy.sh k3 git@bu25 master root`
-* The rest should be automatic! (ignore the warning about backup.dev, and note that haproxy will not start as long as there are no website on your server).
+* The rest should be automatic! (ignore the warning about backup.dev, and note that haproxy will not start as long as there are no websites on your server).
 
 ### Adding an existing website
 * The IndieHosters architecture is migration-oriented, so it aims to make moving a domain from one server to another very easy.
@@ -38,6 +38,8 @@ 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.
+
 ### Adding a new website to your server
 * For each site you want to deploy on the server, e.g. example.com, do the following:
   * Does example.com already exist as a domain name?
-- 
GitLab