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>
63 lines
2.6 KiB
YAML
63 lines
2.6 KiB
YAML
---
|
|
# DATUM Gateway: solo/pooled mining gateway, built from source on knots-box.
|
|
#
|
|
# This is HALF OF A SYSTEM. The Bitcoin Knots node on the same host feeds it via
|
|
# `blocknotify=killall -USR1 datum_gateway` in bitcoin.conf (see
|
|
# roles/bitcoin_knots/README.md). Changing either config means thinking about
|
|
# both. Interrupting Stratum costs mining shares, so check for connected miners
|
|
# before restarting:
|
|
# ss -tn state established '( sport = :23334 )'
|
|
- name: Deploy DATUM Gateway on the bitcoin host
|
|
hosts: bitcoin
|
|
become: yes
|
|
vars_files:
|
|
- ../../services_config.yml
|
|
vars:
|
|
# Preserves the push URL this check reports to. The role knows nothing about
|
|
# Uptime Kuma — this is just "a URL that accepts a ping".
|
|
healthcheck_push_url: "{{ healthcheck_push_urls.datum_gateway | default('') }}"
|
|
roles:
|
|
- datum_gateway
|
|
|
|
- name: Configure Caddy reverse proxy for the DATUM Gateway dashboard on the edge host
|
|
hosts: edge
|
|
become: yes
|
|
vars_files:
|
|
- ../../services_config.yml
|
|
tasks:
|
|
- name: Publish the DATUM Gateway dashboard through Caddy
|
|
ansible.builtin.include_role:
|
|
name: caddy_site
|
|
vars:
|
|
caddy_site_name: datum-gateway
|
|
caddy_site_domain: "{{ subdomains.datum_gateway }}.{{ root_domain }}"
|
|
caddy_site_upstream: "{{ hostvars['knots_box_local'].ansible_host }}:{{ service_settings.datum_gateway.api_port }}"
|
|
caddy_site_resolvers: "100.100.100.100"
|
|
caddy_site_basic_auth:
|
|
- user: "{{ datum_dashboard_username }}"
|
|
hash: "{{ datum_dashboard_password_hash }}"
|
|
|
|
# The role validates its own site fragment; this re-validates the whole
|
|
# assembled Caddyfile, which is the only thing that catches a conflict
|
|
# between two sites.
|
|
- name: Validate the assembled Caddyfile
|
|
ansible.builtin.command: caddy validate --config /etc/caddy/Caddyfile --adapter caddyfile
|
|
changed_when: false
|
|
|
|
- name: Setup public Stratum port forwarding on the edge host
|
|
hosts: edge
|
|
become: yes
|
|
vars_files:
|
|
- ../../services_config.yml
|
|
tasks:
|
|
- name: Expose the DATUM Stratum port through a socket proxy
|
|
ansible.builtin.include_role:
|
|
name: socket_proxy
|
|
vars:
|
|
socket_proxy_name: datum-stratum
|
|
socket_proxy_description: "DATUM Stratum"
|
|
socket_proxy_listen_port: "{{ service_settings.datum_gateway.stratum_port }}"
|
|
socket_proxy_upstream_host: "{{ hostvars['knots_box_local'].ansible_host }}"
|
|
# Matches the UFW comment already on the edge host; the derived default
|
|
# would say "DATUM Stratum" and rewrite the rule.
|
|
socket_proxy_ufw_comment: "DATUM Gateway Stratum public access"
|