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>
54 lines
1.9 KiB
YAML
54 lines
1.9 KiB
YAML
# DATUM Gateway Configuration Variables
|
|
# https://github.com/OCEAN-xyz/datum_gateway
|
|
|
|
# Version - pin to a specific tag
|
|
datum_gateway_version: "v0.4.1beta"
|
|
|
|
# Directories
|
|
datum_gateway_dir: /opt/datum-gateway
|
|
datum_gateway_source_dir: "{{ datum_gateway_dir }}/source"
|
|
datum_gateway_config_dir: /etc/datum-gateway
|
|
datum_gateway_log_dir: /var/log/datum-gateway
|
|
|
|
# Binary
|
|
datum_gateway_bin_path: /usr/local/bin/datum_gateway
|
|
|
|
# Ports
|
|
datum_gateway_stratum_port: "{{ service_settings.datum_gateway.stratum_port }}"
|
|
datum_gateway_api_port: "{{ service_settings.datum_gateway.api_port }}"
|
|
|
|
# Stratum settings
|
|
datum_vardiff_min: 524288 # Minimum share difficulty (must be power of 2; OCEAN floor overrides if higher)
|
|
|
|
# Service user
|
|
datum_gateway_user: datum
|
|
datum_gateway_group: datum
|
|
|
|
# Build options
|
|
datum_gateway_build_jobs: 4
|
|
|
|
# Bitcoin node connection
|
|
# The gateway runs on the same host as Bitcoin Knots so localhost RPC works.
|
|
# datum_bitcoin_rpc_url should include http:// and port.
|
|
datum_bitcoin_rpc_url: "http://127.0.0.1:8332"
|
|
# Note: bitcoin_rpc_user and bitcoin_rpc_password come from group_vars/all/vault.yml
|
|
|
|
# Mining config
|
|
datum_coinbase_tag_primary: "DATUM"
|
|
datum_coinbase_tag_secondary: "BY ORDER OF BIP110"
|
|
|
|
# Both false on the node; the vars file said true. Corrected 2026-09-13 to
|
|
# match reality, on the same basis as datum_mining_address: the running node
|
|
# is authoritative. These control DATUM's pool-password passthrough.
|
|
datum_pool_pass_workers: false
|
|
datum_pool_pass_full_users: false
|
|
datum_pooled_mining_only: true
|
|
|
|
|
|
# --- Health check -----------------------------------------------------------
|
|
# Checks the DATUM Gateway API and records the answer in its exit code, which
|
|
# systemd keeps: `systemctl is-failed datum-gateway-healthcheck.service`.
|
|
#
|
|
# WHERE TO REPORT HEALTH — the one place to plug in monitoring. Empty means
|
|
# check, exit honestly, report nowhere.
|
|
healthcheck_push_url: ""
|