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
|
|
@ -16,7 +16,7 @@
|
|||
# Confinement is a property of the DEPLOYMENT, not of this unit: in a
|
||||
# real swarm the store is its own small VM (the machine is the
|
||||
# boundary); in the all-local case it's a container on the c0re host.
|
||||
# The module hardcodes neither. docs/networking/snapshot-store.md covers what the
|
||||
# The module hardcodes neither. docs/4-implementation/networking/snapshot-store.md covers what the
|
||||
# deployment is expected to provide.
|
||||
{
|
||||
pkgs,
|
||||
|
|
@ -235,7 +235,7 @@ in
|
|||
# nature. The hardening below is defence in depth and NOT a
|
||||
# boundary: a process holding CAP_SYS_ADMIN can call mount(2) and
|
||||
# undo the namespace these directives set up. The real boundary is
|
||||
# the deployment --- see docs/networking/snapshot-store.md.
|
||||
# the deployment --- see docs/4-implementation/networking/snapshot-store.md.
|
||||
systemd.services."swarm-snapshot-store@" = {
|
||||
description = "hyperhive swarm snapshot store receiver";
|
||||
after = [ "swarm-snapshot-store.socket" ];
|
||||
|
|
|
|||
Loading…
Reference in a new issue