counterweight
bf3d21fef7
Nothing in the repo pushes to, authenticates against, or is gated by Uptime
Kuma any more.
── The sixth instance of the banner bug ────────────────────────────────────
memos had `Restart memos` guarded by `uptime_kuma_enabled`, because the
deprecation banner was placed immediately above it and swept it in. It is a
HANDLER, so every memos config change since 2026-09-11 applied to disk and
silently never restarted the service. Ungated.
That is the same failure found in forgejo-runner's self-assert, phoenixd's timer
enable, mempool's three timer enables, fulcrum's restart handler and bitcoind's
restart handler. Every guard was read and asked "monitoring or deployment?"
before being deleted, which is the only reason this was caught.
── What was removed ────────────────────────────────────────────────────────
30 uptime_kuma_enabled guards across 7 unconverted service playbooks, and
the 29 Kuma monitor-creation tasks they gated (embedded Python that drove
the Kuma API, temp credential files, cleanup)
7 dead uptime_kuma_api_url definitions
7 stale DEPRECATED banners
uptime_kuma_enabled and subdomains.uptime_kuma from group_vars/all
healthcheck_push_urls from the vault - 30 push tokens
services/ntfy/setup_ntfy_uptime_kuma_notification.yml -> archive/
The explanatory comments in the six converted roles are KEPT on purpose. They
record why a handler is ungated, and deleting the explanation invites someone
to helpfully re-add the guard.
── The probes moved rather than died ───────────────────────────────────────
Eight per-service health checks were still pushing to Kuma. They are not
superseded by infra/401: that answers "is the unit running", these answer "does
the service actually respond" - an RPC call to bitcoind, a TCP connect to
Fulcrum's Electrum port, an HTTP fetch from Mempool's backend. A process can be
perfectly `active` and useless.
So they were repointed, not deleted. Gatus external endpoints take a POST with
a bearer token and success=true|false where Kuma took a GET with ?status=up, so
report() now maps up/down to true/false internally and no call site changed.
Registered by infra/403 as the `probe` group, one token per host.
Two bugs fixed while in there:
* forgejo-runner's check only ever reported SUCCESS - it exited before pushing
when the runner was down, so a failure was invisible until the heartbeat
window expired. Reporting the failure is the entire point of a check.
* All six healthcheck .service units were mode 0644 and now carry a bearer
token. They are 0600.
Verified: 91 endpoints, 91 UP, 0 DOWN. Every probe triggered by hand and
confirmed arriving. Zero Kuma URLs left in the vault, zero live references in
any playbook or role.
Still standing, deliberately: the Kuma container on watchtower, its Caddy vhost,
and the uptime.contrapeso.xyz DNS record. Turning the service off is a separate
decision from removing the code that talked to it.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
90 lines
5.5 KiB
YAML
90 lines
5.5 KiB
YAML
---
|
|
# Everything, in the order it has to happen.
|
|
#
|
|
# This file is a TABLE OF CONTENTS, not a second source of truth. It says what
|
|
# runs and in what order. It does NOT say which hosts get what — that stays on
|
|
# the `hosts:` line inside each playbook, exactly where it is today. Nothing
|
|
# moves; this file only makes the set readable in one place.
|
|
#
|
|
# What runs on a host? ansible-playbook site.yml --limit <host> --list-hosts
|
|
# Who gets thing Y? the `hosts:` line in Y's own playbook
|
|
# What is a host? ansible-inventory --graph
|
|
#
|
|
# Run a slice with --limit, or run one playbook directly as before. Nothing here
|
|
# changes how any individual playbook behaves.
|
|
|
|
# ── Baseline: every managed machine ─────────────────────────────────────────
|
|
- import_playbook: infra/01_user_and_access_setup_playbook.yml
|
|
- import_playbook: infra/02_firewall_and_fail2ban_playbook.yml
|
|
- import_playbook: infra/900_install_rsync.yml
|
|
- import_playbook: infra/920_join_headscale_mesh.yml
|
|
# Idempotent and kept permanently: guarantees a rebuilt or restored host cannot
|
|
# quietly bring the Uptime-Kuma-era monitoring back.
|
|
- import_playbook: infra/409_remove_legacy_monitoring.yml
|
|
|
|
# ── Monitoring ──────────────────────────────────────────────────────────────
|
|
# Gatus first: the three plays below register endpoints with it, and registering
|
|
# against a host that is not serving yet would simply fail.
|
|
- import_playbook: services/gatus/deploy_gatus_playbook.yml
|
|
- import_playbook: infra/400_host_monitoring.yml
|
|
- import_playbook: infra/401_service_monitoring.yml
|
|
- import_playbook: infra/402_public_monitoring.yml
|
|
# Registers where the per-service probes report. The probes themselves are
|
|
# deployed by each service's own playbook further down; the endpoints must exist
|
|
# before the first push arrives.
|
|
- import_playbook: infra/403_service_probe_registration.yml
|
|
# 910_docker says `hosts: managed`, but only 5 of 11 managed hosts have or need
|
|
# Docker. Left out until it has a [docker] group — see the note in PLAN_7.
|
|
|
|
# ── The hypervisor ──────────────────────────────────────────────────────────
|
|
- import_playbook: infra/nodito/31_proxmox_community_repos_playbook.yml
|
|
- import_playbook: infra/nodito/32_zfs_pool_setup_playbook.yml
|
|
- import_playbook: infra/nodito/34_nut_ups_setup_playbook.yml
|
|
|
|
# ── Reverse proxy, before anything that registers a vhost ───────────────────
|
|
- import_playbook: services/caddy_playbook.yml
|
|
|
|
# ── Services ────────────────────────────────────────────────────────────────
|
|
- import_playbook: services/bitcoin-knots/deploy_bitcoin_knots_playbook.yml
|
|
- import_playbook: services/fulcrum/deploy_fulcrum_playbook.yml
|
|
- import_playbook: services/datum-gateway/deploy_datum_gateway_playbook.yml
|
|
- import_playbook: services/mempool/deploy_mempool_playbook.yml
|
|
- import_playbook: services/memos/deploy_memos_playbook.yml
|
|
- import_playbook: services/forgejo-runner/deploy_forgejo_runner_playbook.yml
|
|
- import_playbook: services/phoenixd/deploy_phoenixd_playbook.yml
|
|
- import_playbook: services/headscale/deploy_headscale_playbook.yml
|
|
- import_playbook: services/vaultwarden/deploy_vaultwarden_playbook.yml
|
|
- import_playbook: services/forgejo/deploy_forgejo_playbook.yml
|
|
- import_playbook: services/lnbits/deploy_lnbits_playbook.yml
|
|
- import_playbook: services/ntfy/deploy_ntfy_playbook.yml
|
|
- import_playbook: services/ntfy-emergency-app/deploy_ntfy_emergency_app_playbook.yml
|
|
- import_playbook: services/personal-blog/deploy_personal_blog_playbook.yml
|
|
|
|
# ── Backups: each source dumps itself, the box pulls ────────────────────────
|
|
- import_playbook: services/headscale/setup_backup_headscale.yml
|
|
- import_playbook: services/vaultwarden/setup_backup_vaultwarden.yml
|
|
- import_playbook: services/forgejo/setup_backup_forgejo.yml
|
|
- import_playbook: services/lnbits/setup_backup_lnbits.yml
|
|
- import_playbook: services/memos/setup_backup_memos.yml
|
|
- import_playbook: playbooks/backups.yml
|
|
|
|
# Deliberately not here. Every playbook in the repo is either imported above or
|
|
# listed below, so this file accounts for all of them:
|
|
#
|
|
# infra/910_docker_playbook.yml says `hosts: managed`, but Docker is on 5
|
|
# of 11 managed hosts and those 5 are exactly
|
|
# the ones that need it. Running it would
|
|
# install Docker on the Bitcoin node and the
|
|
# hypervisor. Needs a [docker] group first.
|
|
#
|
|
# infra/nodito/30_proxmox_bootstrap one-shot: bare-metal bootstrap, run once
|
|
# infra/nodito/33_..._cloud_template one-shot: builds the VM template
|
|
#
|
|
# services/ntfy/setup_ntfy_uptime_ creates a notification channel INSIDE
|
|
# kuma_notification.yml Uptime Kuma. Kuma-specific tooling, not
|
|
# a deployment, and Kuma is being retired.
|
|
#
|
|
# services/vaultwarden/disable_ deliberate manual actions, not convergence
|
|
# vaultwarden_sign_ups_playbook.yml
|
|
# services/personal-blog/setup_
|
|
# deploy_alias_lapy.yml
|