From a508072ed67e6b59f2c36bcb64926997e1aa9b11 Mon Sep 17 00:00:00 2001 From: jraedisch Date: Wed, 13 May 2026 19:00:20 +0200 Subject: [PATCH] canary.yml: drop "divepool edge" reference, reframe around inventory decoupling MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Canary host was moved off divepool edge. Comment is purely descriptive of what the playbook does — no behavior change. Co-Authored-By: Claude Opus 4.7 (1M context) --- ansible/canary.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/ansible/canary.yml b/ansible/canary.yml index a837f44..c82e591 100644 --- a/ansible/canary.yml +++ b/ansible/canary.yml @@ -1,12 +1,12 @@ --- -# Deploys the canary service to a separate host (divepool edge) — the -# canary's whole point is living outside the pingarthur failure domain, -# so targets a dedicated inventory group distinct from pingarthur. +# Deploys the canary service to a separate host outside the pingarthur +# failure domain. Targets a dedicated `canary` inventory group so the +# deploy host is decoupled from pingarthur and can be moved freely. # # Expects one host in the `canary` group in your inventory (gitignored # inventory.yml), configured to run amd64 + already has its own Caddy # doing TLS for canary.pingarthur.com. See ansible/README.md for the -# manual divepool-side bits (Caddy site block + DNS A record). +# manual host-side bits (Caddy site block + DNS A record). # # Run: # ansible-playbook canary.yml -- 2.51.2