counterweight
3711421af5
The four ports were the only entries in services_config.yml with a real
justification: each is read twice, by the role that deploys the service on its
own box AND by a socket-proxy or Caddy play that runs on the EDGE host and
publishes it. A role default is invisible to that second play.
But the shape was wrong in two ways. The file had to be named in vars_files: by
30 plays - opt-in configuration that someone will eventually forget - and five
role defaults silently interpolated service_settings.*, so bitcoin_knots,
fulcrum, datum_gateway and mempool were not self-contained: using any of them
without that one vars_file entry broke it.
Each port now lives in host_vars/<owning box>/main.yml:
host_vars/knots_box_local/main.yml bitcoin_p2p_port, datum_gateway_api_port,
datum_gateway_stratum_port
host_vars/fulcrum_box_local/main.yml fulcrum_ssl_port
host_vars/mempool_box_local/main.yml mempool_frontend_port
host_vars auto-loads and outranks role defaults, so the owning role picks the
value up with no vars_files at all, and the edge play reads the same single
definition as hostvars['<host>'].<name>. The role defaults keep the protocol
standard (8333, 50002, ...) so each role still works standalone, with the live
deployment's value in host_vars winning.
Also fixed a fourth copy of an inventory identity: the mempool Caddy play had
"mempool-box:{{ ... }}" hardcoded in the upstream. It now derives the host from
hostvars['mempool_box_local'].ansible_host, so inventory is the only place any
box's name is written down.
services_config.yml is deleted, with 25 more vars_files entries across 19
playbooks. Between this and the previous commit, 87 vars_files entries are gone
and every variable in the repo now comes from group_vars/all, host_vars,
inventory, a role default, or that service's own *_vars.yml.
Verification: an edge-host probe resolves all eight ports and hostnames to
byte-identical values to the ones services_config.yml used to supply. Each
owning host resolves its own port through host_vars. All 37 playbooks'
--list-tasks output is unchanged. The four edge plays that consume these values
all check-diff changed=0 - the socket-proxy and Caddy units on vipy are
byte-identical, which is the direct proof the rewiring landed on the same
values. fulcrum and datum-gateway check-diff exactly as before (ok=28/changed=1
and ok=15/changed=1, both the known timer re-arm).
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
58 lines
2.1 KiB
YAML
58 lines
2.1 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
|
|
# The edge host's socket-proxy/Caddy play needs this too, and a role default is
|
|
# invisible outside this role. The authoritative value for the live deployment is
|
|
# in host_vars/knots_box_local/main.yml, which outranks this; the value here is the
|
|
# protocol standard, so the role still works standalone.
|
|
datum_gateway_stratum_port: 23334
|
|
datum_gateway_api_port: 7152
|
|
|
|
# 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: ""
|