# 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 infra_secrets.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 infra_secrets.yml

# Network - Fulcrum server
fulcrum_tcp_port: 50001
# Shared with the socket-proxy play on the edge host, so it lives in
# services_config.yml rather than only here.
fulcrum_ssl_port: "{{ service_settings.fulcrum.ssl_port }}"
# 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

# Port forwarding configuration (for public access via VPS)
fulcrum_tailscale_hostname: "{{ service_settings.fulcrum.tailscale_hostname }}"

# 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