Configurable CRON schedule

[i20]

Hello !

First thing first thank you so much for this great script, it makes my life so much easier <3

I would like to submit a feature request to make the CRON schedule customizable via the envvars like most of the rest.
Actually the CRON schedule is autoset on a random time but in my case I need to be able to choose it explicitly to avoid any issues with other scheduled tasks I have.

Until now I have to sh into the docker container after each (re)creation to crontab -e what makes the container auto update a little bit tedious.

Any thoughts ?

[jdevera]

This is a cool idea, especially because when a certificate is renewed, it can trigger a bunch of service reloads that can introduce downtime, and it is sometimes important to control when that happens.

I think a problematic area here is that acme.sh installs a cron job in the image at build time.

In any case, in the meantime, you can work around that without needing for manual intervention by not running acme.sh in dameon mode but instead using a container such as whefter/docker-cron to do docker run $youracmecontainer --cron --home "/root/.acme.sh" --config-home "/acme.sh"

[i20]

Yes I thought about your suggestion but in my case I kinda like having all the configuration the closest possible to the acme.sh container to simplify things for future me trying to get back at it months or years later ^^' That way I only need to care about that container existence/run and "nothing else" to know if certificate renewal is on or not, nevertheless thank you for the tip !

A customizable envvar would perfectly fit my need without being too harsh to implement I think :)

[Neilpang]

you can use acme.sh --uninstall-cronjob to clean the default cronjob.

And then do whatever you like.