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

gateway_nginx: fix stale module doc + clarify reload log (argus nits)

Browse source
This commit is contained in:
atlas 2026-05-31 22:41:21 +02:00 • committed by mara
commit 3b76842853
1 changed files with 14 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

22
hive-c0re/src/gateway_nginx.rs
View file

@ -1,13 +1,16 @@
//! Runtime nginx include-file generator for the gateway's per-agent //! Runtime nginx include-file generator for the gateway's per-agent
//! `/agent/<name>/` location blocks (#869). //! `/agent/<name>/` location blocks.
//! //!
//! Writes `/var/lib/hyperhive/gateway/agents.conf` on every topology change. //! Writes `/var/lib/hyperhive/gateway/agents.conf` on every topology change.
//! The gateway container bind-mounts the whole `/var/lib/hyperhive/` //! The gateway container bind-mounts `/var/lib/hyperhive/gateway/` (NOT the
//! directory at `/run/hive-state/` and nginx includes //! whole parent dir) at `/run/hive-state/`; nginx includes
//! `/run/hive-state/agents.conf`. A systemd path unit inside the //! `/run/hive-state/agents.conf`. After each write, c0re triggers
//! gateway container watches the file and triggers `nginx -s reload` //! `nginx -s reload` inside the gateway container via
//! on every atomic rename — no `nixos-rebuild switch` needed when //! `systemd-run --machine=hive-gateway` from the host — no `nixos-rebuild
//! agents start, stop, or flip `useUnixSocket`. //! switch` needed when agents start, stop, or flip `useUnixSocket`.
//! (A path unit inside the container was tried first but `IN_MOVED_TO`
//! from the atomic rename does not cross the nspawn mount-namespace
//! boundary — see #889 for the failure analysis.)
//! //!
//! Upstream selection mirrors `agent_sockets::build_map`: an agent //! Upstream selection mirrors `agent_sockets::build_map`: an agent
//! gets a UDS upstream when its `.bound` marker exists (harness has //! gets a UDS upstream when its `.bound` marker exists (harness has
@ -168,7 +171,10 @@ fn reload_gateway_nginx() {
.status(); .status();
match status { match status {
Ok(s) if s.success() => { Ok(s) if s.success() => {
tracing::debug!("gateway nginx reloaded successfully"); // systemd-run accepted the request; nginx reload runs
// asynchronously inside the container and may still fail
// silently, but that's acceptable given the best-effort contract.
tracing::debug!("systemd-run accepted gateway nginx reload request");
} }
Ok(s) => { Ok(s) => {
tracing::warn!( tracing::warn!(