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
|
|
@ -289,7 +289,7 @@ async fn systemd_daemon_reload() -> Result<()> {
|
|||
}
|
||||
|
||||
/// Append the bind flag for `child`'s `state` dir into `binds`. See
|
||||
/// docs/agent-lifecycle/persistence.md ("Cross-agent access to state") for what
|
||||
/// docs/2-handbook/agent-lifecycle/persistence.md ("Cross-agent access to state") for what
|
||||
/// the holder may touch and why. Creates the missing host-side directory so
|
||||
/// nspawn doesn't refuse to start; a missing dir is non-fatal.
|
||||
///
|
||||
|
|
@ -362,7 +362,7 @@ fn holds_manage_root_agent(agent_name: &str, path: &Path) -> bool {
|
|||
/// that hive-c0re owns: `PRIVATE_NETWORK` (always 1), `HOST_ADDRESS` (the
|
||||
/// bridge gateway IP) and `EXTRA_NSPAWN_FLAGS` (the runtime-dir bind). What
|
||||
/// those network vars mean and why isolation is unconditional:
|
||||
/// `docs/networking/network.md` § *What the Rust side does*.
|
||||
/// `docs/4-implementation/networking/network.md` § *What the Rust side does*.
|
||||
///
|
||||
/// ⚠️ The start script expands `$EXTRA_NSPAWN_FLAGS` unquoted into the
|
||||
/// `systemd-nspawn` command.
|
||||
|
|
|
|||
Loading…
Reference in a new issue