d9d4193854e8d495db145eee72cb6eae78055415
haproxy-letsencrypt-docker.md
| ... | ... | @@ -19,8 +19,9 @@ There's a few things that make this a bit of a hassle: |
| 19 | 19 | 4. When the certs are renewed, we'll need to tell haproxy to pick them up<br/>Some docker-in-docker magic is required. |
| 20 | 20 | 5. certbot doesn't know how to make haproxy-complicit cert pem files<br/>We'll need to do a little scripting. |
| 21 | 21 | |
| 22 | -# Stage 0 - network setup |
|
| 22 | +# Stage 0 - setup |
|
| 23 | 23 | This all assumes that your soon-to-be certificated domains' A records are all pointing at the docker host (or port-forwarding router, or whatever), and you can reach the docker host on port 80 and 443 from the Interwebs. |
| 24 | +Your docker host should have docker and docker-compose installed, and docker running. |
|
| 24 | 25 | |
| 25 | 26 | # Stage 1 - get some certs |
| 26 | 27 | Since this is a greenfield setup, we can let certbot take care of the initial cert request on its own - HAProxy should be down for this. |