Files
jwinterm a455c60ed0 docs: operator console guide + fix example recipes + document all env vars
- New docs/operations/CONSOLE.md: reaching /admin, NIP-98 login, the
  defaults->env->DB precedence model, per-section runtime-safe vs
  restart-required table, expected_versions concurrency, restart_apply_mode
  (with the systemd Restart=always requirement for auto), clearing a DB
  override. Linked from README + OPERATOR_SETUP.
- All six example recipes gained an explicit chain-enablement block
  (FEATURE_XMR/WOW on, BTC/LTC/GRIN off) so they no longer hard-fail
  Config::validate in production (default-on chains with empty sources).
- Documented all 16 previously-undocumented env vars in .env.example
  (RESTART_APPLY_MODE, TOR_ADMIN_ONION, DEPLOYMENT_MODE, TIP_SHARE_BASE_URL,
  ...); RELAY.md gained the premium-post policy + RELAY_WRITE_ALLOWLIST_NPUBS;
  ADMIN_PUBKEYS noted as reserved/inert.
2026-07-19 15:52:07 -04:00
..

personal — your own sovereign backend

Run the backend for yourself alone: no registration gates, unlimited restore, the relay optional. The smallest footprint; you are the only user.

  • Config: .env.example — all gates off, WALLET_RESTORE_POLICY=unlimited, relay off.
  • Boot: copy .env.example → .env, generate the secrets (openssl rand -hex 32), fill your chain endpoints, run the binary (migrations apply on boot). Bind the API to 127.0.0.1 behind your own TLS.
  • Non-custodial: the backend never sees your seed or spend keys — funds stay on-chain.