counterweight
954b683c71
Three files existed only as second copies of things group_vars/all already
auto-loads, and 34 playbooks named them in vars_files: - which outranks
group_vars, so the copies won. The day someone edited one and not the other,
those plays would silently keep the stale value. infra_vars.yml was already
drifting: group_vars/all/main.yml had grown age_backup_recipient and
backup_pull_public_key that it lacked.
infra_vars.yml - a strict subset of group_vars/all/main.yml
infra_secrets.yml - decrypts byte-identical to group_vars/all/vault.yml
infra_secrets.yml.example - documented Uptime Kuma credentials as the reason
the file exists, which stopped being true
Deleted, along with 62 vars_files entries across 34 playbooks (12 of which
named ../../group_vars/all/main.yml directly - same defect, a vars_files entry
duplicating an auto-loaded file at higher precedence than the file itself).
Checked before touching anything: infra_secrets.yml was listed LAST in 10 plays,
after services_config.yml, so removal would flip precedence if the two shared a
key. They share none, and neither does services_config.yml with
group_vars/all/main.yml, so the removal is provably inert.
services_config.yml was the last one standing. It held four unrelated things:
caddy_sites_dir - an identical copy of roles/caddy_site/defaults/.
Deleted; the role default is now the only one.
*.tailscale_hostname (x3) - a THIRD copy of each box's identity, which
inventory.ini already holds as ansible_host.
Deleted. Edge plays now read
hostvars['<host>'].ansible_host - verified an
edge play resolves that with nothing loaded and
the other host in no play. Three copies of one
name is how bitcoin_rpc_host ended up labelled
"knots_box" while pointing at fulcrum-box.
subdomains, ntfy topic, - genuinely global: their readers span managed,
headscale namespace monitoring, vpn_control and edge, so no single
group covers them. Moved to group_vars/all/main.yml
where they auto-load. The ntfy_topic and
headscale_namespace indirection through
service_settings collapses to the global name.
the four cross-host ports - the only entries with a real justification.
Left in place; they move in the next commit.
Also dead, all Uptime Kuma residue or duplication:
phoenixd_monitor_name, forgejo_runner healthcheck_timeout_seconds/retries,
fulcrum_tailscale_hostname, and bitcoin_knots_version - the last being a
v-prefixed copy of bitcoin_knots_version_short that nothing read, two
hand-maintained copies of one version string.
Corrected a false comment: services_config.yml claimed the uptime_kuma subdomain
"no longer resolves to anything". It resolves to 164.92.239.72 and answers HTTP
302, and 11 playbooks still template it. Same wrong premise as PLAN_3.
Verification: all 37 playbooks' --list-tasks output is byte-identical before and
after. A probe resolving all 22 values services_config.yml used to supply returns
21 identical and one intended deletion (caddy_sites_dir, now role-only - confirmed
the role still resolves it: "Ensure Caddy sites-enabled directory exists" comes
back ok against the real path). memos check-diff identical before and after.
Syntax passes on every playbook.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
59 lines
2.4 KiB
YAML
59 lines
2.4 KiB
YAML
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
|
|
|
|
# age recipient for all backup artefacts
|
|
age_backup_recipient: "age192wwdaseqej2ggwyp884gtm05c396anp7chr0vr8m47g50fahpyqr9fsza"
|
|
|
|
# Public key small-backups-box pulls with
|
|
# Authorised on each source host for an unprivileged, dedicated user only
|
|
backup_pull_public_key: "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOfIixKMhA9z+Nvyx6ToZIniC8aEgyiInRiboaTTemgX offsite-backup-pull"
|
|
|
|
|
|
# ─────────────────────────────────────────────────────────────────────────────
|
|
# Subdomains. Global because the edge host proxies for services that live on
|
|
# other machines, so no single inventory group covers the readers. Combine with
|
|
# root_domain above to build an FQDN.
|
|
#
|
|
# Moved here from services_config.yml, which 30 plays had to remember to name in
|
|
# vars_files: - a file everyone must opt into is a file someone will forget.
|
|
# ─────────────────────────────────────────────────────────────────────────────
|
|
subdomains:
|
|
# Monitoring (watchtower)
|
|
ntfy: ntfy
|
|
# Uptime Kuma IS still running and this subdomain DOES resolve
|
|
# (164.92.239.72, HTTP 302). Only the Ansible code and the vault credentials
|
|
# were retired. A comment here previously claimed the opposite.
|
|
uptime_kuma: uptime
|
|
|
|
# VPN infrastructure (spacey)
|
|
headscale: headscale
|
|
|
|
# Core services (vipy)
|
|
vaultwarden: vault
|
|
forgejo: forgejo
|
|
lnbits: wallet
|
|
|
|
# Secondary services (vipy)
|
|
ntfy_emergency_app: avisame
|
|
personal_blog: pablohere
|
|
|
|
# Memos (memos-box)
|
|
memos: memos
|
|
|
|
# Mempool block explorer (mempool-box, proxied via vipy)
|
|
mempool: mempool
|
|
|
|
# DATUM Gateway dashboard (knots-box, proxied via vipy)
|
|
datum_gateway: datum
|
|
|
|
# Read by plays targeting managed, monitoring, vpn_control and edge - no one
|
|
# group covers them, so these are global rather than group_vars/<group>.
|
|
ntfy_topic: alerts
|
|
headscale_namespace: counter-net
|