docs: sort the top-level directories into five sections by what the reader wants
Every docs directory moves under 1-getting-started, 2-handbook, 4-implementation or 5-project; the options reference (section 3) comes from the website and has no directory here. trust-boundary stays whole under the handbook for now. web-ui, swarm and tools split between handbook and implementation, and the command-line references move to 2-handbook/reference. Links, path references in code and nix, and the docs index follow the moves; no page content changes.
This commit is contained in:
parent
53ccbcb4b3
commit
6739bb903d
1 changed files with 736 additions and 701 deletions
|
|
@ -1,7 +1,7 @@
|
|||
# The swarm's binary cache: an attic server in a `swarm-attic` container on the
|
||||
# host that sets `deploy.attic.enable`, which `deploy.allSwarmServices` defaults
|
||||
# on where the host has the cache's store identity. The swarm builder pushes
|
||||
# green builds to it (docs/swarm/builder.md).
|
||||
# green builds to it (docs/4-implementation/swarm/builder.md).
|
||||
#
|
||||
# Two host units run under the cache's own store leaf, the shape
|
||||
# ./swarm-grafana.nix gives its admin password. One creates the key atticd signs
|
||||
|
|
@ -269,7 +269,7 @@ in
|
|||
For an external cache, set
|
||||
services.hyperhive.deploy.attic.enable = lib.mkForce false; where the
|
||||
shared services are hosted ("To use an external cache, override the two
|
||||
defaults and don't set `deploy.attic.enable` anywhere", docs/swarm/builder.md).
|
||||
defaults and don't set `deploy.attic.enable` anywhere", docs/4-implementation/swarm/builder.md).
|
||||
For the swarm's own cache, drop the override of
|
||||
services.hyperhive.swarm.attic.domain.
|
||||
'';
|
||||
|
|
|
|||
Loading…
Reference in a new issue