873618a8362ee70d25b3f8ac1064225769a4fa47
haproxy-letsencrypt-docker.md
| ... | ... | @@ -221,7 +221,7 @@ networks: |
| 221 | 221 | haproxy: |
| 222 | 222 | ``` |
| 223 | 223 | Here we have: |
| 224 | -* The container_name is 'haproxy'. We'll be referring to this container name later on for sending signals when certs are renewed. |
|
| 224 | +* The container_name is 'haproxy'. We'll be referring to this container name later on for sending signals when certs are renewed (referenced in the deploy-hook script from stage 1). |
|
| 225 | 225 | * The 'haproxy/bind' dir is mounted at /usr/local/etc/haproxy, so the haproxy.cfg file we created is in the right place for haproxy to read it. Mounted read-only, and with the 'Z' selinux flag (I'm running RedHat-ish host OSes here, so it's required - leave off the ',Z' if docker complains). |
| 226 | 226 | * The letsencrypt volume is mounted at /etc/letsencrypt so haproxy can read the cert file. |
| 227 | 227 | * We're creating a user-defined network called 'haproxy' so we can talk to other containers and have built-in dns work. |