vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

docs(3191): the gateway's comments describe a host service, not a container

Browse source 
Prose-only sweep of every remaining claim that nginx or dnsmasq lives
in a container: the port comment (root in a container -> root on the
host), upstreamHost's netns rationale, the ACME state dir, the store
path reachability note, the vhost tree header, dnsmasq's resolv.conf
paragraph (there is no copy and no path unit watching it any more),
the two hive-network bridge comments, and swarm-controller's socket
access-control note, which described a bind-mount that no longer
exists.

No behaviour change; all of it was describing a mechanism that was
deleted.
This commit is contained in:
atlas 2026-08-12 12:20:28 +02:00
commit f85724a638
7 changed files with 54 additions and 59 deletions
Download patch file Download diff file Expand all files Collapse all files

22
nix/host-modules/hive-gateway/options.nix
View file

@ -28,10 +28,10 @@ in
example = 8080;
description = ''
TCP port the gateway listens on. Default 80 (canonical web
port). nginx inside the container binds <1024 because the
container's init runs as root; if 80 is already taken on the
host (existing nginx, traefik, etc.) override to an unused
port like 8080 or move the conflicting service.
port). nginx runs on the host as root, so it can bind <1024;
if 80 is already taken on the host (existing nginx, traefik,
etc.) override to an unused port like 8080 or move the
conflicting service.
'';
};
@ -40,8 +40,8 @@ in
default = "127.0.0.1";
description = ''
Host the gateway proxies non-static requests to. Defaults to
`127.0.0.1` because the gateway container shares the host
netns, so loopback resolves directly to hive-c0re.
`127.0.0.1` because nginx runs on the host itself, so loopback
resolves directly to hive-c0re.
'';
};
@ -180,11 +180,11 @@ in
default = false;
example = true;
description = ''
Let nginx inside the gateway container obtain and renew TLS
certificates automatically via ACME (Let's Encrypt). When
enabled, each vhost calls out to Let's Encrypt using the
HTTP-01 challenge on `port` (default 80) and stores certs
inside the gateway container's persistent state dir.
Let the gateway's nginx obtain and renew TLS certificates
automatically via ACME (Let's Encrypt). When enabled, each
vhost calls out to Let's Encrypt using the HTTP-01
challenge on `port` (default 80) and stores certs in the
gateway's persistent state dir on the host.
Requirements:
- `services.hyperhive.domain` must be set and publicly