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
2 changed files with 736 additions and 701 deletions
|
|
@ -16,6 +16,6 @@ admin socket.
|
|||
## Shape
|
||||
|
||||
Serde-derived request/response types only — no server or client logic. Both
|
||||
sides import them so the shapes stay in sync. See `docs/trust-boundary/boundary.md` +
|
||||
`docs/trust-boundary/security.md` for the privilege boundary these types sit on, and
|
||||
sides import them so the shapes stay in sync. See `docs/2-handbook/trust-boundary/boundary.md` +
|
||||
`docs/2-handbook/trust-boundary/security.md` for the privilege boundary these types sit on, and
|
||||
`hive-priv/README` for the helper itself.
|
||||
|
|
|
|||
|
|
@ -190,7 +190,7 @@ pub struct CredentialMount {
|
|||
/// Network isolation parameters for `WriteNspawnFlags`. hive-priv writes
|
||||
/// `PRIVATE_NETWORK=1` + veth bridge wiring from these; every container
|
||||
/// is isolated, so they are required rather than a mode selector.
|
||||
/// No static address is pre-assigned here — see `docs/networking/network.md`
|
||||
/// No static address is pre-assigned here — see `docs/4-implementation/networking/network.md`
|
||||
/// § *Container isolation* for how a container gets its address.
|
||||
#[derive(Debug, Clone, Serialize, Deserialize)]
|
||||
pub struct NetworkIsolation {
|
||||
|
|
@ -201,7 +201,7 @@ pub struct NetworkIsolation {
|
|||
/// container-side setup installs a default route (`default via <gw>`)
|
||||
/// before DHCP completes: without it the container has no route off
|
||||
/// the bridge subnet until the DHCP lease arrives. The same IP runs the
|
||||
/// hive dnsmasq resolver — see `docs/networking/network.md` § *How the isolated
|
||||
/// hive dnsmasq resolver — see `docs/4-implementation/networking/network.md` § *How the isolated
|
||||
/// container gets its resolver*.
|
||||
pub gateway_ip: String,
|
||||
}
|
||||
|
|
|
|||
Loading…
Reference in a new issue