|
|
|
|
|
|
by vog
3142 days ago
|
|
|
> I have certbot running in one Docker container, the .well-known route directing to the one dedicated Docker host running certbot, and whenever certbot renews the certificate, it writes the cert to the NAS share that is only mounted on the LBs and then triggers a SIGKILL to the haproxy docker containers (which causes haproxy to re-read the cert file and configuration). Is this really more stable than a simple cronjob? It is far more complicated, for sure, so there should be significant benefits to make up for that. |
|
|