docs: the forge is swarm-wide but not optional, so it derives nothing
Both the option description and docs/swarm.md listed the forge among the services whose `enable` defaults from `swarm.enableRequiredServices`. It has no `enable`: it is the canonical store for the meta flake and every agent's config repo, so it deploys with hyperhive itself. The distinction is worth stating rather than deleting — a reader who sees matrix and authelia listed and the forge absent would reasonably wonder whether the forge is per-hive. It isn't; it's mandatory.
This commit is contained in:
parent
8d21a47f42
commit
ade0bf24c5
2 changed files with 19 additions and 8 deletions
|
|
@ -116,8 +116,8 @@ swarm's trust hierarchy.
|
|||
## Running the swarm's shared services
|
||||
|
||||
Some things exist once per **swarm**, not once per hive: the forge, the
|
||||
matrix homeserver, the SSO provider, the CA. Two options say where they
|
||||
live, and everything else derives:
|
||||
matrix homeserver, the SSO provider, the CA. Two options say where the
|
||||
optional ones live, and everything else derives:
|
||||
|
||||
```nix
|
||||
services.hyperhive.enableAllLocalDefaults = true; # everything on this box
|
||||
|
|
@ -137,6 +137,11 @@ operator saying so rather than something inferred. With them off, a hive
|
|||
is a *client* of those services — it configures how to reach them and
|
||||
runs none of them.
|
||||
|
||||
The forge is the exception, and not because it is per-hive: it is
|
||||
swarm-wide but **not optional**, being the canonical store for the meta
|
||||
flake and every agent's config repo, so it deploys with hyperhive itself
|
||||
and has no `enable` to derive from anything.
|
||||
|
||||
### SSO (authelia)
|
||||
|
||||
One authelia per swarm, in a `swarm-authelia` container, at
|
||||
|
|
|
|||
Loading…
Reference in a new issue