mara/hyperhive
mara/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Activity

fixup! docs: sort the top-level directories into five sections by what the reader wants

Browse source
This commit is contained in:
iris 2026-11-06 18:34:41 +01:00 • committed by mara
commit 0e10473e6f
1 changed files with 49 additions and 49 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/2-handbook/swarm/services.md
View file

@ -439,7 +439,7 @@ doesn't gate them: that option says this host _runs_ the store, while the swarm
has one either way, reached by its swarm name through the gateway.
Agent-side configuration, and what a hive's own collector does, are in
[`../scheduler/observability.md`](../../4-implementation/scheduler/observability.md).
[`4-implementation/scheduler/observability.md`](../../4-implementation/scheduler/observability.md).
### CI runner
@ -452,7 +452,7 @@ It needs neither the forge nor a hive on its host. It reaches the forge at
publishes to the secret store, which it reads under its own `ci-runner` leaf.
On a host without the store, that leaf is the one file to copy. Registration,
the container and the threat model are in
[`../scheduler/ci.md`](../../4-implementation/scheduler/ci.md).
[`4-implementation/scheduler/ci.md`](../../4-implementation/scheduler/ci.md).
The runner's built-in Prometheus endpoint is on, bound to `127.0.0.1:9101` in
the container's own network namespace. The container's journal forwarder