chore: scrub #NNN issue references from code comments and nix descriptions
Part of the docs-migration chore (issue #708). Remove GitHub issue numbers from inline comments, option descriptions, and rustdoc — these are contextless noise for anyone reading the code without access to the original discussions. Replace with prose that captures the same rationale directly. No functional change. Build still clean (cargo check passes).
This commit is contained in:
parent
083a100ba1
commit
188f3ea5ec
18 changed files with 131 additions and 151 deletions
|
|
@ -10,8 +10,7 @@ let
|
|||
hyperhiveDomain = config.services.hyperhive.domain;
|
||||
|
||||
# ROOT_URL forgejo advertises in clone links + outbound URLs. When
|
||||
# served behind the gateway (#749 — mara verdict at issue:9609,
|
||||
# sub-domain over sub-path), `cfg.domain` doubles as both the
|
||||
# served behind the gateway, `cfg.domain` doubles as both the
|
||||
# forgejo `DOMAIN` setting AND the gateway vhost server-name, so
|
||||
# ROOT_URL just uses it directly (drops the port suffix when the
|
||||
# gateway is on the canonical port 80). When direct (gateway off
|
||||
|
|
@ -83,18 +82,16 @@ in
|
|||
Public hostname for the forge. Doubles as both the forgejo
|
||||
`DOMAIN` setting (clone URLs forgejo advertises) AND the
|
||||
gateway vhost server-name when `behindGateway = true`
|
||||
(#749, mara verdict at issue:9609 — sub-domain over sub-path).
|
||||
(sub-domain routing — see `docs/gateway.md`).
|
||||
|
||||
Defaults to `forge.''${services.hyperhive.domain}` when the
|
||||
hive-domain is set (idiomatic sub-domain shape — `forge`
|
||||
labelled under the hive's bare domain), falling back to
|
||||
`localhost` otherwise (pre-#749 direct-on-port behaviour).
|
||||
`localhost` otherwise (direct-on-port behaviour).
|
||||
|
||||
Set to a full hostname (`git.example.com`,
|
||||
`forge.internal.lan`, etc.) for a bespoke vhost shape — the
|
||||
full domain goes here, no separate sub-domain-label option
|
||||
(mara on #754:9684 — "specify full forge domain in options
|
||||
instead").
|
||||
full domain goes here, no separate sub-domain-label option.
|
||||
'';
|
||||
};
|
||||
|
||||
|
|
@ -120,8 +117,7 @@ in
|
|||
description = ''
|
||||
Serve forgejo through the hive-gateway nginx as a sub-domain
|
||||
vhost (`server_name = cfg.domain`) instead of directly on
|
||||
`httpPort` (#749, mara verdict at issue:9609 — sub-domain
|
||||
over sub-path).
|
||||
`httpPort` (sub-domain routing — see `docs/gateway.md`).
|
||||
|
||||
When `true`:
|
||||
- The gateway adds a `server { server_name = ''${cfg.domain}; }`
|
||||
|
|
@ -137,11 +133,10 @@ in
|
|||
gateway is running (e.g. an external git client that doesn't
|
||||
traverse the gateway).
|
||||
|
||||
The mara-call on #749:9609 picks sub-domain over sub-path for
|
||||
forge + matrix (both are external standard apps with sub-domain-
|
||||
native config defaults). Per-agent UIs stay on sub-path
|
||||
(`/agent/<name>/`) because they're hyperhive-internal +
|
||||
already base-path-aware via #731.
|
||||
Sub-domain routing is the preferred shape for forge + matrix
|
||||
(both are external standard apps with sub-domain-native config
|
||||
defaults). Per-agent UIs stay on sub-path (`/agent/<name>/`)
|
||||
because they're hyperhive-internal + already base-path-aware.
|
||||
'';
|
||||
};
|
||||
|
||||
|
|
@ -171,18 +166,18 @@ in
|
|||
example = true;
|
||||
description = ''
|
||||
Open `httpPort` + `sshPort` in the host firewall. Off by
|
||||
default (#651, secure-by-default): the forge is reachable
|
||||
from the host + every agent container via `localhost` either
|
||||
way (shared netns), so the firewall opens only matter for
|
||||
access from outside the host. Flip to `true` when you want
|
||||
the operator's browser / external git clients to hit the
|
||||
forge directly. (The container shares host netns, so this
|
||||
is the only firewall layer that matters.)
|
||||
default (secure-by-default): the forge is reachable from the
|
||||
host + every agent container via `localhost` either way
|
||||
(shared netns), so the firewall opens only matter for access
|
||||
from outside the host. Flip to `true` when you want the
|
||||
operator's browser / external git clients to hit the forge
|
||||
directly. (The container shares host netns, so this is the
|
||||
only firewall layer that matters.)
|
||||
|
||||
**Breaking change as of #651**: this used to default to
|
||||
`true`. If you relied on the old default for external
|
||||
reach, add `services.hyperhive.forge.openFirewall = true;`
|
||||
to your host config before rebuilding.
|
||||
**Breaking change**: this used to default to `true`. If you
|
||||
relied on the old default for external reach, add
|
||||
`services.hyperhive.forge.openFirewall = true;` to your host
|
||||
config before rebuilding.
|
||||
'';
|
||||
};
|
||||
};
|
||||
|
|
|
|||
Loading…
Reference in a new issue