No description

Find a file

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
ansible	uptime-kuma: add uptime_kuma_enabled flag and make monitoring blocks inert	2026-09-11 22:43:55 +02:00
archive/uptime_kuma	archive: record Uptime Kuma monitors and setup before decommissioning	2026-09-11 22:43:15 +02:00
tofu/nodito	mempool working	2025-12-14 22:15:29 +01:00
.gitignore	track inventory	2026-09-11 21:32:23 +02:00
01_infra_setup.md	more stuff	2025-12-01 11:17:02 +01:00
02_vps_core_services_setup.md	phoenixd upgrade	2026-08-08 15:19:11 +02:00
03_vm_disk_enlargement.md	little thingies	2026-03-22 21:25:08 +01:00
README.md	secrets note in readme	2026-09-11 20:08:19 +02:00
requirements.txt	lots of stuff man	2025-11-06 23:09:44 +01:00

Personal infra

My repo documenting my personal infra, along with artifacts, scripts, etc.

How to use

Go through the different numbered markdowns in the repo root to do the different parts.

ansible-vault edit ansible/your_file_with_secrets.yml

Assumes that you've set ansible/.vault_pass with chmod 600.