fix(deploy): halkyon.li's heavy sidecars started after every boot (ADR 0039, D6)

A reboot or a power cut between 01:55 and 05:00 left them stopped until the
next morning: halkyon-morning.timer now also fires two minutes after boot.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me>
This commit is contained in:
Tizian 「ティツィアーン」 2026-11-10 20:00:58 +01:00
commit 086b980947
Signed by: raisondetredev
GPG key ID: 07F6FCF405488B64

View file

@ -1,11 +1,15 @@
# halkyon-morning.service at 05:00:00 daily (ADR 0039, D6). As
# halkyon-morning.service at 05:00:00 daily (ADR 0039, D6), and two minutes after every
# boot: a reboot or a power cut inside the window would otherwise leave the heavy sidecars
# stopped (unless-stopped keeps a stopped container so) until the next morning. The
# runner's own timer never catches up after a boot, so they don't meet. As
# /etc/systemd/system/halkyon-morning.timer, enabled with
# `systemctl enable --now halkyon-morning.timer`.
[Unit]
Description=halkyon.li: night.sh start at 05:00:00
Description=halkyon.li: night.sh start at 05:00:00 and after boot
[Timer]
OnCalendar=*-*-* 05:00:00
OnBootSec=2min
Persistent=false
[Install]