personal_infra/ansible/infra_vars.yml

new_user: counterweight
ssh_port: 22
allow_ssh_from: "any"
root_domain: contrapeso.xyz

# Uptime Kuma was decommissioned on 2026-09-11. The monitoring blocks in the
# playbooks are kept deliberately — the check logic is meant to be rewired to
# whatever replaces it. This flag keeps them inert until then. See archive/uptime_kuma/.
uptime_kuma_enabled: false
wip 2025-07-01 10:39:01 +02:00			`new_user: counterweight`
thingies 2025-07-01 16:14:44 +02:00			`ssh_port: 22`
wip 2025-07-01 10:39:01 +02:00			`allow_ssh_from: "any"`
uptime kuma works 2025-07-01 17:02:28 +02:00			`root_domain: contrapeso.xyz`
uptime-kuma: add uptime_kuma_enabled flag and make monitoring blocks inert Removing the credentials would otherwise break these playbooks mid-deploy: they template uptime_kuma_password with no assert to stop them first. 100 tasks are now guarded by uptime_kuma_enabled (false), so deployments run normally and the monitoring sections skip. A further 28 tasks were already self-guarding on monitor_setup/push_url being defined; verified that a skipped task's registered variable makes those skip cleanly rather than error. The blocks are kept on purpose — the health-check logic is the durable part and should be rewired to whatever replaces Uptime Kuma. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> 2026-09-11 22:43:55 +02:00
			`# Uptime Kuma was decommissioned on 2026-09-11. The monitoring blocks in the`
			`# playbooks are kept deliberately — the check logic is meant to be rewired to`
			`# whatever replaces it. This flag keeps them inert until then. See archive/uptime_kuma/.`
			`uptime_kuma_enabled: false`