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
|
|
@ -362,7 +362,7 @@ in
|
|||
# the host running it decides is below — which responder build it runs and
|
||||
# the store identities its units present. `enable` already lives in
|
||||
# ./deploy.nix, which also carries the renames. The callout's keys are no
|
||||
# option at all: they live in the secret store (docs/swarm/credentials.md).
|
||||
# option at all: they live in the secret store (docs/2-handbook/swarm/credentials.md).
|
||||
options.services.hyperhive.deploy.nats = {
|
||||
monitorPort = lib.mkOption {
|
||||
type = lib.types.port;
|
||||
|
|
|
|||
Loading…
Reference in a new issue