85848dc3d719853d50e92b166a41b8d05bb4280a
haproxy-letsencrypt-docker.md
| ... | ... | @@ -291,7 +291,7 @@ What doing? |
| 291 | 291 | * We're mounting the letsencrypt volume back up at /etc/letsencrypt so 'certbot --renew' can operate on the certs. |
| 292 | 292 | * The docker socket from the host is mounted at /var/run/docker.sock. This lets us do docker operations from inside the container. |
| 293 | 293 | * There's a small sleep to let haproxy start up (ewww, but also, whatever), then we attempt a renew and run the deploy-hook script (see stage 1) if anything changed. |
| 294 | -* The deploy-hook script concatenates the cert chain and key into an haproxy style .pem file, then sends a SIGHUP via the docker command to the haproxy container, telling it to re-read its config. |
|
| 294 | +* The deploy-hook script concatenates the cert chain and key into an haproxy style .pem file, then sends a SIGHUP via the docker command to the haproxy container, telling haproxy to re-read its config and pick up the new certs |
|
| 295 | 295 | * The container is granted privileged permissions to let the docker socket work. |
| 296 | 296 | |
| 297 | 297 | ## Go! |