personal_infra/ansible
counterweight b07ed72a92
caddy: add a [caddy] role group and target it
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>
2026-09-11 23:03:25 +02:00
..
group_vars/all uptime-kuma: add uptime_kuma_enabled flag and make monitoring blocks inert 2026-09-11 22:43:55 +02:00
host_vars/nodito vars 2026-09-11 22:17:13 +02:00
infra uptime-kuma: deprecation banners on the monitoring-only plays 2026-09-11 22:43:55 +02:00
services caddy: add a [caddy] role group and target it 2026-09-11 23:03:25 +02:00
ansible.cfg now using password 2026-09-11 17:59:41 +02:00
infra_secrets.yml uptime-kuma: remove credentials from the vaults 2026-09-11 22:43:15 +02:00
infra_secrets.yml.example uptime-kuma: remove credentials from the vaults 2026-09-11 22:43:15 +02:00
infra_vars.yml uptime-kuma: add uptime_kuma_enabled flag and make monitoring blocks inert 2026-09-11 22:43:55 +02:00
inventory.ini caddy: add a [caddy] role group and target it 2026-09-11 23:03:25 +02:00
requirements.yml uptime-kuma: annotate config and drop the unused collection 2026-09-11 22:43:56 +02:00
services_config.yml uptime-kuma: annotate config and drop the unused collection 2026-09-11 22:43:56 +02:00