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>
78 lines
3.7 KiB
YAML
78 lines
3.7 KiB
YAML
# Fulcrum Configuration Variables
|
|
|
|
# Version - Pinned to specific release
|
|
fulcrum_version: "2.1.0" # Fulcrum version to install
|
|
|
|
# Directories
|
|
fulcrum_db_dir: /mnt/fulcrum_data/fulcrum_db # Database directory (heavy data on special mount)
|
|
fulcrum_config_dir: /etc/fulcrum # Config file location (standard OS path)
|
|
fulcrum_lib_dir: /var/lib/fulcrum # Other data files (banner, etc.) on OS disk
|
|
fulcrum_binary_path: /usr/local/bin/Fulcrum
|
|
|
|
# Network - Bitcoin RPC connection
|
|
# Bitcoin Knots is on a different host (knots_box_local)
|
|
# Using RPC user/password authentication (credentials from group_vars/all/vault.yml)
|
|
# Addressed by Tailscale name, never a LAN IP. This was
|
|
# bitcoin_rpc_host: "192.168.1.140" # IP of knots_box_local
|
|
# but .140 is fulcrum-box ITSELF - knots-box is .135. The DHCP leases had
|
|
# reshuffled (the same drift that transposed the inventory), so running this
|
|
# playbook would have pointed Fulcrum at itself and broken indexing. The live
|
|
# config had already been hand-corrected to knots-box; this makes the repo
|
|
# agree with it.
|
|
bitcoin_rpc_host: "knots-box"
|
|
bitcoin_rpc_port: 8332 # Bitcoin Knots RPC port
|
|
# Note: bitcoin_rpc_user and bitcoin_rpc_password are loaded from group_vars/all/vault.yml
|
|
|
|
# Network - Fulcrum server
|
|
fulcrum_tcp_port: 50001
|
|
# 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/fulcrum_box_local/main.yml, which outranks this; the value here is the
|
|
# protocol standard, so the role still works standalone.
|
|
fulcrum_ssl_port: 50002
|
|
# Binding address for Fulcrum TCP/SSL server:
|
|
# - "127.0.0.1" = localhost only (use when Caddy is on the same box)
|
|
# - "0.0.0.0" = all interfaces (use when Caddy is on a different box)
|
|
# - Specific IP = bind to specific network interface
|
|
fulcrum_tcp_bind: "0.0.0.0" # Default: localhost (change to "0.0.0.0" if Caddy is on different box)
|
|
fulcrum_ssl_bind: "0.0.0.0" # Binding address for SSL port
|
|
# If Caddy is on a different box, set this to the IP address that Caddy will use to connect
|
|
|
|
# SSL/TLS Configuration
|
|
fulcrum_ssl_enabled: true
|
|
fulcrum_ssl_cert_path: "{{ fulcrum_config_dir }}/fulcrum.crt"
|
|
fulcrum_ssl_key_path: "{{ fulcrum_config_dir }}/fulcrum.key"
|
|
fulcrum_ssl_cert_days: 3650 # 10 years validity for self-signed cert
|
|
|
|
|
|
# Performance
|
|
# db_mem will be calculated as 75% of available RAM automatically in playbook
|
|
# db_mem is computed as this share of RAM unless fulcrum_db_mem_mb is set
|
|
# explicitly. On a 5931 MB host 75% is 4448 MB, which leaves ~1.4 GB for the
|
|
# OS and for Fulcrum's non-cache memory; the live config had been hand-tuned
|
|
# down to 2048 and that setting is respected below.
|
|
fulcrum_db_mem_percent: 0.75 # 75% of RAM for database cache
|
|
|
|
# Configuration options
|
|
fulcrum_anon_logs: true # Anonymize client IPs and TxIDs in logs
|
|
fulcrum_peering: false # Disable peering with other Fulcrum servers
|
|
fulcrum_zmq_allow_hashtx: true # Allow ZMQ hashtx notifications
|
|
|
|
# Service user
|
|
fulcrum_user: fulcrum
|
|
fulcrum_group: fulcrum
|
|
|
|
|
|
# --- Health check -----------------------------------------------------------
|
|
# Checks the Electrum TCP port and records the answer in its exit code, which
|
|
# systemd keeps: `systemctl is-failed fulcrum-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: ""
|
|
|
|
# Explicit db_mem in MB. When set it wins over fulcrum_db_mem_percent; empty
|
|
# means compute from RAM. Set here because the live host had been hand-tuned to
|
|
# 2048 and a silent jump to 4448 is not something a refactor should do.
|
|
fulcrum_db_mem_mb_override: 2048
|