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>
73 lines
3.1 KiB
YAML
73 lines
3.1 KiB
YAML
# Bitcoin Knots Configuration Variables
|
|
|
|
# Version - REQUIRED: Specify exact version/tag to build
|
|
# The only version string. There used to be a second, v-prefixed copy
|
|
# (bitcoin_knots_version) that nothing read - two hand-maintained copies of one
|
|
# fact, with nothing keeping them in step.
|
|
bitcoin_knots_version_short: "29.2.knots20251110"
|
|
|
|
# Directories
|
|
bitcoin_knots_dir: /opt/bitcoin-knots
|
|
bitcoin_knots_source_dir: "{{ bitcoin_knots_dir }}/source"
|
|
bitcoin_data_dir: /var/lib/bitcoin # Standard location for config, logs, wallets
|
|
bitcoin_large_data_dir: /mnt/knots_data # Custom location for blockchain data (blocks, chainstate)
|
|
bitcoin_conf_dir: /etc/bitcoin
|
|
|
|
# Network
|
|
bitcoin_rpc_port: 8332
|
|
# Shared with the socket-proxy play on the edge host, so it lives in
|
|
# services_config.yml rather than only here.
|
|
bitcoin_p2p_port: "{{ service_settings.bitcoin.p2p_port }}"
|
|
bitcoin_rpc_bind: "0.0.0.0"
|
|
|
|
# Build options
|
|
bitcoin_build_jobs: 4 # Parallel build jobs (-j flag), adjust based on CPU cores
|
|
bitcoin_build_prefix: /usr/local
|
|
|
|
# Configuration options
|
|
bitcoin_enable_txindex: true # Set to true if transaction index needed (REQUIRED for Electrum servers like Electrs/ElectrumX)
|
|
bitcoin_max_connections: 125
|
|
# dbcache will be calculated as 90% of host RAM automatically in playbook
|
|
|
|
# ZMQ Configuration
|
|
bitcoin_zmq_enabled: true
|
|
bitcoin_zmq_bind: "tcp://0.0.0.0"
|
|
bitcoin_zmq_port_rawblock: 28332
|
|
bitcoin_zmq_port_rawtx: 28333
|
|
bitcoin_zmq_port_hashblock: 28334
|
|
bitcoin_zmq_port_hashtx: 28335
|
|
|
|
# Service user
|
|
bitcoin_user: bitcoin
|
|
bitcoin_group: bitcoin
|
|
|
|
# --- Health check ----------------------------------------------------------
|
|
# Checks bitcoind RPC and records the answer in its exit code, which systemd
|
|
# keeps: `systemctl is-failed bitcoin-knots-healthcheck.service`.
|
|
#
|
|
# WHERE TO REPORT HEALTH — the one place to plug in monitoring. Empty means
|
|
# check, exit honestly, report nowhere. Any endpoint accepting an HTTP ping
|
|
# works; nothing here is specific to a monitoring product.
|
|
healthcheck_push_url: ""
|
|
|
|
# --- Logging ----------------------------------------------------------------
|
|
# The live node logs to a file. Set to "" to use printtoconsole=1 (journald).
|
|
bitcoin_logfile: "{{ bitcoin_data_dir }}/debug.log"
|
|
|
|
# --- dbcache ----------------------------------------------------------------
|
|
# Computed as 90% of RAM unless this is set. The live node was hand-tuned to
|
|
# 200 MB; the calculation would have produced 3528. As with fulcrum, note that
|
|
# set_fact outranks role defaults, so the CALCULATION has to honour this - a
|
|
# value pinned only in defaults/ is silently ignored.
|
|
bitcoin_dbcache_mb_override: 200
|
|
|
|
# --- DATUM Gateway ----------------------------------------------------------
|
|
# This node feeds block templates to datum_gateway on knots-box. These settings
|
|
# were hand-added to bitcoin.conf and were missing from the template, so a
|
|
# playbook run would have removed them and broken the mining setup.
|
|
bitcoin_datum_gateway_enabled: true
|
|
bitcoin_blockmaxsize: 3985000
|
|
bitcoin_blockmaxweight: 3985000
|
|
bitcoin_blocknotify: "killall -USR1 datum_gateway"
|
|
bitcoin_maxmempool: 1000
|
|
bitcoin_blockreconstructionextratxn: 1000000
|