docs(#3255): record the controller's first persisted file
The crate's module doc claimed no persistence and no writes, which this change makes false, and docs/persistence.md had no swarm-controller entry at all — the webhook secret is the daemon's first persisted state.
This commit is contained in:
parent
b2596097d8
commit
645fd0d56c
2 changed files with 25 additions and 5 deletions
|
|
@ -3,11 +3,14 @@
|
|||
//! `services.hyperhive.swarm.controller.enable` on, and serves HTTP over a
|
||||
//! unix socket that the hive-gateway's nginx proxies to.
|
||||
//!
|
||||
//! Holds one piece of read-only state: the swarm's hive directory, loaded
|
||||
//! once at startup from an env var the NixOS module sets
|
||||
//! (`services.hyperhive.swarm.controller`) — see `load_hives`. Still no
|
||||
//! persistence and no writes; a config change means a redeploy, same as
|
||||
//! every other option this process reads.
|
||||
//! Configuration is read-only and loaded once at startup from env vars the
|
||||
//! NixOS module sets (`services.hyperhive.swarm.controller`) — see
|
||||
//! `load_hives`. A config change means a redeploy, same as every other
|
||||
//! option this process reads.
|
||||
//!
|
||||
//! The one thing it does persist is `webhook-secret` under its
|
||||
//! `StateDirectory` (see `webhook`), because that key is handed to Forgejo
|
||||
//! at registration and so cannot be regenerated per boot.
|
||||
//!
|
||||
//! Distinct from `hive-c0re`, which is per-hive: c0re owns the agents on
|
||||
//! one host, this owns what is true across hives.
|
||||
|
|
|
|||
Loading…
Reference in a new issue