Replies: 1 comment
-
check out this blog post and consider running the script directly on the NAS. It simplify's everything greatly. You can write a small shell script to schedule the renewals that renews the cert then deploy's it to your systems. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I use acme.sh in a Docker container on Synology NAS no. 1, not as a daemon, just as a run-and-remove container.
On NAS no. 1, I have used acme.sh to issue and deploy a wildcard certificate, that I would also like to deploy on Synology NAS no. 2 and also on another machine no. 3 using ssh.
I can deploy to NAS no. 1 from no. 1, no problem. I use
--deploy-hook synology_dsm
.I can also deploy to NAS no. 2 from no. 1 using
--deploy-hook synology_dsm
.And finally, I can deploy to machine no. 3 from NAS no. 1 using
--deploy-hook ssh
.However, I can't figure out how to run the container using
--cron
to renew the certificate and automatically redeploy to all three locations. Is there a way to do this in one command? I have tried to use--reloadcmd
with the first--deploy
but that does not seem to work (the reload command script doesn't run).Or do I have to use
--no-cron
initially, then later--renew
via a scheduled task, and then do three separate manual deployments (assuming the renewal is successful)?Thanks!
Beta Was this translation helpful? Give feedback.
All reactions