Yes, I’m going to be bad and delete the question template; I think the question is a little more general.
I’m putting a cert onto a a FreePBX system using DNS validation, which means I can’t use the built-in cert management. The method I’m following (see https://community.freepbx.org/t/lets-encrypt-dns-challenge-and-scripting/65903 for discussion) is using acme.sh to issue, followed by a separate acme.sh --install-cert command to put the files in the right place and reload the appropriate FreePBX services. It seems to work well so far.
That server also has Webmin on it, and I’d want to use the same cert for that service. But it wants the cert file in a different format (cat key cert > miniserv.pem), and in a different place. So my question is, if I run acme.sh --install-cert again with different locations and a different reload command, what will happen on renewal? Will acme.sh perform both “install” procedures? Or will the second replace the first?
The alternative, of course, is to create a simple script and call that from the reload command–also pretty simple. But if the first way would work, it would seem like more of a “clean” way to go.
--renew-hook Command to be run once for each successfully renewed certificate.
--deploy-hook The hook file to deploy cert
--reloadcmd "service nginx reload" After issue/renew, it's used to reload the server.
I see that the descriptions are different, but I don't see any difference in the practical effect of these three, except that --renew-hook does not run when you first issue/install a cert (and even that isn't explicit in the docs). Other than that, I guess, "deploy" more accurately describes "copy and modify files and restart a service" than "reload" does, why should I prefer one over the other?