dank/serverAppConfigs
1
0
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects Releases Wiki Activity

caddy: drop the systemctl enable; the quadlet generator already enables it

Browse Source 
podman's quadlet generator creates the default.target.wants symlink from
the unit's [Install] section at every user-manager start (is-enabled
reports 'generated' for all healthy quadlets, pihole included). An
explicit 'systemctl --user enable caddy.service' fails with 'transient or
generated' and aborted the deploy after the unit was already installed.
This commit is contained in:
Frank
2026-08-26 20:19:03 -07:00
parent f3c1ac1823
commit 868c8cfbca
4 changed files with 15 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/deployment_flow.bats
+6 -3
View File
@@ -56,10 +56,13 @@ load helpers
@test "canonical Caddy deployment installs its boot-persistent quadlet" {
# 2026-08-26: a bare compose container never came back after reboot.
# deploy_caddy must install, enable, and start the quadlet unit instead
# of `podman-compose up`.
# deploy_caddy must install and start the quadlet unit instead of
# `podman-compose up`. Boot persistence comes from the quadlet generator's
# default.target.wants symlink (is-enabled reports "generated"), so there
# is no explicit systemctl enable — it fails on generated units.
grep -q 'install_quadlet caddy dankclaw/caddy/quadlet caddy' "$REPO_ROOT/scripts/deploy-remote.sh"
grep -q 'systemctl --user enable caddy.service' "$REPO_ROOT/scripts/deploy-remote.sh"
grep -q 'systemctl --user restart caddy.service' "$REPO_ROOT/scripts/deploy-remote.sh"
! grep -q 'systemctl --user enable caddy.service' "$REPO_ROOT/scripts/deploy-remote.sh"
! grep -q 'podman-compose -f dankclaw/compose.yaml up -d --no-deps caddy' "$REPO_ROOT/scripts/deploy-remote.sh"
! grep -q 'no proxy was stopped or replaced' "$REPO_ROOT/scripts/deploy-remote.sh"
}