# Mempool Configuration Variables

# Version - Pinned to specific release
mempool_version: "v3.2.1"

# Directories
mempool_dir: /opt/mempool
mempool_data_dir: "{{ mempool_dir }}/data"
mempool_mysql_dir: "{{ mempool_dir }}/mysql"

# Network - Bitcoin Core/Knots connection (via Tailnet Magic DNS)
bitcoin_host: "knots-box"
bitcoin_rpc_port: 8332
# Note: bitcoin_rpc_user and bitcoin_rpc_password are loaded from group_vars/all/vault.yml

# Network - Fulcrum Electrum server (via Tailnet Magic DNS)
fulcrum_host: "fulcrum-box"
fulcrum_port: 50001
fulcrum_tls: "false"

# Mempool network mode
mempool_network: "mainnet"

# Container ports (internal)
# 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/mempool_box_local/main.yml, which outranks this; the value here is the
# protocol standard, so the role still works standalone.
mempool_frontend_port: 8080
mempool_backend_port: 8999

# MariaDB settings
mariadb_database: "mempool"
mariadb_user: "mempool"
# Note: mariadb_mempool_password is loaded from group_vars/all/vault.yml



# --- Health checks ----------------------------------------------------------
# Three independent checks, because Mempool is three moving parts and knowing
# WHICH one is down is the whole point. Each records its answer in its exit
# code, which systemd keeps:
#     systemctl is-failed mempool-backend-healthcheck.service
#
# push_url is where to report, and is the single plug-in point for whatever
# monitoring exists. Empty means check, exit honestly, report nowhere.
# The URLs are credentials, so callers pass them from the vault.
healthcheck_push_token: ""

mempool_healthchecks:
  - name: mariadb
    label: MariaDB
    push_url: ""
  - name: backend
    label: Backend
    push_url: ""
  - name: frontend
    label: Frontend
    push_url: ""