acme: fix service_triggers on config change
authorFlorian Eckert <redacted>
Fri, 21 Mar 2025 09:20:21 +0000 (10:20 +0100)
committerToke Høiland-Jørgensen <redacted>
Tue, 1 Apr 2025 20:53:08 +0000 (22:53 +0200)
commit420210b3184237d60c5b1e81d186fe8d1b05c177
tree6ceb1e9f3af2fa287659deb213e9c79f5b9febe8
parentea285eb4606fcea851efe85d744a95782c06c62a
acme: fix service_triggers on config change

In the current implementation, the config change trigger is no longer set
at boot time. This is because during boot, only the '$CHALLENGE_DIR' is
created with the boot function. The 'start_service' is first called by first
cron call at midnight. This call is installing the service_triggers reload
handling.

To fix this, add a new extra_command 'renew' that is responsible to renew
the acme. This function is called from cron and the start_service
function does the rest.

* Create directories
* Install service reload trigger form acme config change

Fixes: 76f17ab15b (acme-common: Create challenge directory on boot)
Signed-off-by: Florian Eckert <redacted>
net/acme-common/files/acme.init
net/acme-common/files/acme.uci-defaults
git clone https://git.99rst.org/PROJECT