counterweight
6c1bcbed95
552-line playbook becomes 18 lines plus a 411-line role
(install/service/healthcheck phases, four templates, two handlers).
phoenixd_vars.yml is deleted; its content is the role's defaults.
Task-list diff vs the old playbook shows ONLY the eight Uptime Kuma tasks
removed - everything else identical and in the same order.
phoenixd holds a Lightning node, so the run was checked against a pre-flight:
before: channel 6c25fa83..., balanceSat 1550723, capacitySat 3114830,
blockHeight 966692, active since 2026-09-02
after: identical, and still active since 2026-09-02 - it did NOT restart
`Create phoenixd systemd service` came back unchanged, which is what proves the
template reproduces the live unit byte-for-byte. changed=3 was the health check
script, its unit (Environment rename), and the timer restart. Second run:
changed=0.
Two things the conversion fixed, both symptoms of the deprecation banner having
been applied to contiguous blocks rather than to individual tasks:
- The health check logged "ERROR: UPTIME_KUMA_PUSH_URL not set" on every fire -
about 1,400 times a day - because its Environment= was emptied at
decommissioning. The exit code was still correct so nothing was broken, but it
is exactly the kind of noise that trains you to ignore a log. An unset push
URL is now normal and silent.
- `Enable and start phoenixd health check timer` was guarded by
uptime_kuma_enabled and so had not run since the decommissioning, while the
timer itself was still live on the host from before. Ansible had quietly
stopped managing something that was still running. Ungated.
Noted, not changed: seed.dat is mode 0644 on the host. That is phoenixd's own
doing, but it is a Lightning seed and worth tightening.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
54 lines
2 KiB
YAML
54 lines
2 KiB
YAML
# phoenixd Configuration Variables
|
|
# https://phoenix.acinq.co/server
|
|
|
|
# Version - pin to a specific release tag
|
|
phoenixd_version: "0.9.0"
|
|
phoenixd_arch: "linux-x64"
|
|
phoenixd_url: "https://github.com/ACINQ/phoenixd/releases/download/v{{ phoenixd_version }}/phoenixd-{{ phoenixd_version }}-{{ phoenixd_arch }}.zip"
|
|
|
|
# Service user
|
|
phoenixd_user: phoenix
|
|
phoenixd_group: phoenix
|
|
|
|
# Directories
|
|
phoenixd_home: /opt/phoenixd
|
|
# phoenixd resolves its data dir from PHOENIX_DATADIR; seed.dat, phoenix.conf
|
|
# and the channel db all live here.
|
|
phoenixd_data_dir: "{{ phoenixd_home }}/.phoenix"
|
|
phoenixd_bin_dir: /usr/local/bin
|
|
|
|
# Lightning settings
|
|
phoenixd_chain: mainnet
|
|
# Amount automatically requested when inbound liquidity is needed: off, 2m, 5m, 10m
|
|
phoenixd_auto_liquidity: "2m"
|
|
# Max mining fee for on-chain operations, in sats. Empty means phoenixd's default.
|
|
phoenixd_max_mining_fee: ""
|
|
# Required for non-interactive deployment
|
|
phoenixd_agree_tos: true
|
|
|
|
# HTTP API
|
|
# Stays on loopback: phoenixd is never exposed through Caddy, only local
|
|
# consumers (e.g. LNBits on the same host) talk to it.
|
|
phoenixd_http_bind_ip: "127.0.0.1"
|
|
phoenixd_http_bind_port: 9740
|
|
|
|
# Optional webhook for payment events. Leave empty to disable.
|
|
phoenixd_webhook_url: ""
|
|
|
|
phoenixd_monitor_name: "Phoenixd"
|
|
|
|
|
|
|
|
# --- Health check -----------------------------------------------------------
|
|
# The check asks phoenixd itself whether it is healthy (service active AND the
|
|
# node answers getinfo with a nodeId) and records the answer in its exit code,
|
|
# which systemd keeps:
|
|
# systemctl is-failed phoenixd-healthcheck.service
|
|
# That is a complete answer with no monitoring system involved.
|
|
phoenixd_healthcheck_script_path: /usr/local/bin/phoenixd-healthcheck-push.sh
|
|
phoenixd_healthcheck_service_name: phoenixd-healthcheck
|
|
|
|
# WHERE TO REPORT HEALTH — the one place to plug in monitoring.
|
|
# Empty means check, log, exit honestly, report nowhere. Any endpoint that
|
|
# accepts an HTTP ping works; nothing here is specific to a monitoring product.
|
|
healthcheck_push_url: ""
|