dank/serverAppConfigs
1
0
Fork 0
Code Issues 6 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
scripts/deploy-remote.sh
+6 -1
View File
@@ -322,8 +322,13 @@ deploy_caddy() {
# lives in host volumes, so removing the container loses nothing.
podman stop caddy >/dev/null 2>&1 || true
podman rm caddy >/dev/null 2>&1 || true
# install_quadlet runs daemon-reload, which re-runs podman's quadlet
# generator: it creates caddy.service AND the default.target.wants symlink
# from the unit's [Install] section (is-enabled reports "generated" —
# that is the healthy state for a quadlet; an explicit systemctl enable
# fails on generated units). Boot persistence comes from the generator,
# same as pihole/gitea/searxng/open-webui.
install_quadlet caddy dankclaw/caddy/quadlet caddy
systemctl --user enable caddy.service
systemctl --user restart caddy.service
if podman container exists caddy; then
local reloaded=0