From daa665939c18a7873059f8cd9f48938cddaed864 Mon Sep 17 00:00:00 2001
From: Michiel de Jong <michiel@unhosted.org>
Date: Tue, 18 Nov 2014 13:41:10 +0000
Subject: [PATCH] reflect startssl T&C
---
doc/deploying-a-server.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/deploying-a-server.md b/doc/deploying-a-server.md
index 91370dd..3b1fbc8 100644
--- a/doc/deploying-a-server.md
+++ b/doc/deploying-a-server.md
@@ -57,7 +57,7 @@ Make sure you read [getting started](getting-started-as-a-hoster.md) first.
* For the 'wordpress' image, all you need is the TLS certificate. Use the 'static-git' image if you already have some static
content that should go on there, and which you can put in a public git repository somewhere.
* Unless you already have a TLS certificate for example.com, get one
- (from StartSSL or elsewhere), and concatenate the certificate
+ (from StartSSL if you own the domain in question, from namecheap or elsewhere if you do not), and concatenate the certificate
and its unencrypted private key into one file.
* Make sure the TLS certificate is valid (use `scripts/check-cert.sh` for this), and scp it to `/data/import/example.com/TLS/example.com.pem` on k3.
* Now ssh into k3, and if for instance 'wordpress' is the image you chose, run:
--
GitLab