4 commits

Author	SHA1	Message	Date
counterweight	2dabc6ad62	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
counterweight	c14d61d090	stuff	2025-12-07 19:02:50 +01:00
counterweight	c8754e1bdc	lots of stuff man	2025-11-06 23:09:44 +01:00
Pablo Martin	eddde5e53a	uptime kuma works	2025-07-01 17:02:28 +02:00

Renamed from ansible/vars.yml (Browse further)