services/caddy_playbook.yml was the one play still targeting a location group (vps) rather than a role group. The two coincide today — vps is exactly vipy, watchtower and spacey, the three hosts with /etc/caddy/sites-enabled — but adding a fourth VPS that does not run Caddy would have silently pulled it into the play. [caddy:children] is edge + monitoring + vpn_control. Verified the play selects the same three machines before and after. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| bitcoin-knots | ||
| datum-gateway | ||
| forgejo | ||
| forgejo-runner | ||
| fulcrum | ||
| headscale | ||
| lnbits | ||
| memos | ||
| mempool | ||
| ntfy | ||
| ntfy-emergency-app | ||
| personal-blog | ||
| phoenixd | ||
| vaultwarden | ||
| caddy_playbook.yml | ||