From 2be2e851cb4b0456e22896e246b247d9f1f7f019 Mon Sep 17 00:00:00 2001 From: Garrett Allen <98648590+Gerrrt@users.noreply.github.com> Date: Tue, 22 Sep 2026 20:35:28 +0000 Subject: [PATCH] docs(systemd): the firewall unit stops justifying WorkingDirectory with a dependency that is gone MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The comment said backup-firewall.sh resolves backups/firewall and .sops.yaml relative to the process's directory, and made WorkingDirectory= load-bearing for this unit in a way it is not for its siblings. That was true when written and stopped being true at d0e2556, which anchored both to the script's own repository so a hand-run export lands where backup-offsite.sh reads it. Nothing breaks either way — the directive is still set and still correct. What a stale justification costs is the next reader, who is told the opposite of how the script works and could reasonably undo the anchoring to match the comment. Replaced with the siblings' reason: the same value everywhere keeps the five units from disagreeing about where the repository is. Comment only, so there is nothing to deploy. The installed copy under /etc/systemd/system carries the old text until the next make install-timers, and systemd does not read comments. systemd-analyze verify passes; make validate passes. Refs #611. Co-Authored-By: Claude Opus 5 --- systemd/homelab-backup-firewall.service | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/systemd/homelab-backup-firewall.service b/systemd/homelab-backup-firewall.service index d25e2a93..a9dccd92 100644 --- a/systemd/homelab-backup-firewall.service +++ b/systemd/homelab-backup-firewall.service @@ -5,8 +5,15 @@ # stops the stack nor reads the private key. # # See homelab-backup-volumes.service for why each directive below is set. -# WorkingDirectory= matters more here than anywhere else: backup-firewall.sh -# resolves backups/firewall and .sops.yaml relative to the process's directory. +# WorkingDirectory= used to matter more here than anywhere else, because +# backup-firewall.sh resolved backups/firewall and .sops.yaml relative to the +# process's directory. It no longer does (#611): both are anchored to the +# script's own repository, so an export taken by hand from somewhere else lands +# where backup-offsite.sh reads it rather than somewhere nothing looks — which +# is how a ninety-day visit came to carry two kinds while reporting three. +# The directive stays for the reason the siblings give, that the same value +# everywhere keeps the units from disagreeing about where the repository is, +# and not because this one breaks without it. [Unit] Description=HomeLab: export and encrypt the pfSense configuration Documentation=file:///home/robo/code/Gerrrt/HomeLab/docs/runbooks/schedule-maintenance.md