Skip to content
Snippets Groups Projects
Commit daa66593 authored by Michiel de Jong's avatar Michiel de Jong
Browse files

reflect startssl T&C

parent 703827ce
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
doc/deploying-a-server.md
+ 1
− 1
View file @ daa66593
...@@ -57,7 +57,7 @@ Make sure you read [getting started](getting-started-as-a-hoster.md) first. ...@@ -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 * 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. 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 * 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. 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. * 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: * Now ssh into k3, and if for instance 'wordpress' is the image you chose, run:
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment