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>
53 lines
2 KiB
YAML
53 lines
2 KiB
YAML
# phoenixd Configuration Variables
|
|
# https://phoenix.acinq.co/server
|
|
|
|
# Version - pin to a specific release tag
|
|
phoenixd_version: "0.9.0"
|
|
phoenixd_arch: "linux-x64"
|
|
phoenixd_url: "https://github.com/ACINQ/phoenixd/releases/download/v{{ phoenixd_version }}/phoenixd-{{ phoenixd_version }}-{{ phoenixd_arch }}.zip"
|
|
|
|
# Service user
|
|
phoenixd_user: phoenix
|
|
phoenixd_group: phoenix
|
|
|
|
# Directories
|
|
phoenixd_home: /opt/phoenixd
|
|
# phoenixd resolves its data dir from PHOENIX_DATADIR; seed.dat, phoenix.conf
|
|
# and the channel db all live here.
|
|
phoenixd_data_dir: "{{ phoenixd_home }}/.phoenix"
|
|
phoenixd_bin_dir: /usr/local/bin
|
|
|
|
# Lightning settings
|
|
phoenixd_chain: mainnet
|
|
# Amount automatically requested when inbound liquidity is needed: off, 2m, 5m, 10m
|
|
phoenixd_auto_liquidity: "2m"
|
|
# Max mining fee for on-chain operations, in sats. Empty means phoenixd's default.
|
|
phoenixd_max_mining_fee: ""
|
|
# Required for non-interactive deployment
|
|
phoenixd_agree_tos: true
|
|
|
|
# HTTP API
|
|
# Stays on loopback: phoenixd is never exposed through Caddy, only local
|
|
# consumers (e.g. LNBits on the same host) talk to it.
|
|
phoenixd_http_bind_ip: "127.0.0.1"
|
|
phoenixd_http_bind_port: 9740
|
|
|
|
# Optional webhook for payment events. Leave empty to disable.
|
|
phoenixd_webhook_url: ""
|
|
|
|
|
|
|
|
|
|
# --- Health check -----------------------------------------------------------
|
|
# The check asks phoenixd itself whether it is healthy (service active AND the
|
|
# node answers getinfo with a nodeId) and records the answer in its exit code,
|
|
# which systemd keeps:
|
|
# systemctl is-failed phoenixd-healthcheck.service
|
|
# That is a complete answer with no monitoring system involved.
|
|
phoenixd_healthcheck_script_path: /usr/local/bin/phoenixd-healthcheck-push.sh
|
|
phoenixd_healthcheck_service_name: phoenixd-healthcheck
|
|
|
|
# WHERE TO REPORT HEALTH — the one place to plug in monitoring.
|
|
# Empty means check, log, exit honestly, report nowhere. Any endpoint that
|
|
# accepts an HTTP ping works; nothing here is specific to a monitoring product.
|
|
healthcheck_push_url: ""
|