hermes-proxy — OpenAI-compatible HTTP egress on :8645. Shares the same OAuth credentials as the gateway via hermes_gateway_data volume. Reachable only via the hermes_proxy overlay (internal: true).
voice-gateway — Python aiohttp WS bridge between browser and hermes-proxy. Placement node.hostname==rudolf-T. Image is built externally by Gitea Actions in Org1/hermes-voice-gateway (workflow release.yml on tag push) and pulled from gitea.rudolf.keenetic.link/hermes/hermes-voice-gateway.
Piper voice model is downloaded on first start via entrypoint.sh from HuggingFace.
History
0054d9c — initial: add hermes-proxy + voice-gateway to hermes_infra stack
c55a40b — fix: drop shell default syntax from HERMES_PROXY_TOKEN
24ede4a — fix: drop HERMES_PROXY_TOKEN env (auth skipped for MVP)
c2f1b06 — fix: hardcode voice-gateway image tag to v0.3.0 (brencher's ${version} substitution emits auto-<sha> tags that don't exist)
f9f2253 — fix: correct hermes-proxy command (proxy start, not proxy run — the actual argparse rejects run as invalid choice)
## Summary
Two new services in the `hermes_infra` stack:
1. **`hermes-proxy`** — OpenAI-compatible HTTP egress on :8645. Shares the same OAuth credentials as the gateway via `hermes_gateway_data` volume. Reachable only via the `hermes_proxy` overlay (`internal: true`).
2. **`voice-gateway`** — Python aiohttp WS bridge between browser and hermes-proxy. Placement `node.hostname==rudolf-T`. Image is built externally by Gitea Actions in `Org1/hermes-voice-gateway` (workflow `release.yml` on tag push) and pulled from `gitea.rudolf.keenetic.link/hermes/hermes-voice-gateway`.
Piper voice model is downloaded on first start via `entrypoint.sh` from HuggingFace.
## History
- `0054d9c` — initial: add hermes-proxy + voice-gateway to hermes_infra stack
- `c55a40b` — fix: drop shell default syntax from HERMES_PROXY_TOKEN
- `24ede4a` — fix: drop HERMES_PROXY_TOKEN env (auth skipped for MVP)
- `c2f1b06` — fix: hardcode voice-gateway image tag to v0.3.0 (brencher's `${version}` substitution emits `auto-<sha>` tags that don't exist)
- `f9f2253` — fix: correct hermes-proxy command (`proxy start`, not `proxy run` — the actual argparse rejects `run` as invalid choice)
## Verification
- [ ] `docker stack deploy -c hermes_squid/stack-compose.yml hermes_infra` succeeds
- [ ] `hermes_infra_hermes-proxy` task running, listening on :8645
- [ ] `hermes_infra_voice-gateway` task running on rudolf-T
- [ ] `curl http://rudolf-T:8765/healthz` returns `{"status":"ok"}`
- [ ] Browser → voice-gateway WS → hermes-proxy → Hermes round-trip works
## Related
- Org1/hermes-voice-gateway#4 (voice-gateway service + browser client) — closed, code lives in main
- admin/ansible#7 closed (Gitea ROOT_URL fix)
Routes /v1/chat/completions to the same OAuth backend the gateway uses,
via a shared hermes_gateway_data volume. Bound to 127.0.0.1 inside the
container; reachable only via the hermes_proxy overlay (internal: true).
Defaults to aiohttp on :8645 (hermes_cli/proxy/server.py DEFAULT_PORT).
Targets rudolf-T consumers (voice-gateway, Org1/hermes-voice-gateway#3)
that need an OpenAI-shaped transport to the agent without going through
the gateway's messaging adapters.
Two changes to the hermes_infra stack:
1. New 'hermes-proxy' service: OpenAI-compatible HTTP egress on :8645,
sharing the same OAuth credentials as the gateway (shared volume
hermes_gateway_data). Reachable only via the hermes_proxy overlay
(internal: true). Image nousresearch/hermes-agent:v2026.8.3 with
command 'proxy run --host 0.0.0.0 --port 8645'.
2. New 'voice-gateway' service: Python aiohttp WS bridge between browser
and hermes-proxy. Placement node.hostname==rudolf-T (x86_64 worker,
14.5 GiB RAM). Image is built externally by Gitea Actions in
Org1/hermes-voice-gateway (workflow release.yml on tag push) and
pulled from gitea.rudolf.keenetic.link/hermes/hermes-voice-gateway.
Piper voice model (ru_RU-denis-medium.onnx + .json) is downloaded
on first start via the container's entrypoint.sh from HuggingFace.
No pre-baked volume needed.
Image tags in registry: v0.1.1, v0.2.0. Bump via git tag + push in
Org1/hermes-voice-gateway, then update compose.yaml image tag here.
brencher parses ${VAR} via re.sub on the literal token name. ${HERMES_PROXY_TOKEN:-}
collapses to the token 'HERMES_PROXY_TOKEN:-' which is not in the env dict, raising
KeyError at deploy step. Plain ${HERMES_PROXY_TOKEN} resolves to empty string when
the env is unset, which is what the shell default was protecting against.
hermes-proxy listens on hermes_proxy overlay which is internal:true —
no external ingress. Auth between voice-gateway and hermes-proxy is not
required for MVP, and brencher was rejecting the ${HERMES_PROXY_TOKEN}
substitution as missing key.
Removing the line lets brencher apply the compose; the gateway already
connects unauthenticated when the env is absent.
brencher's ${version} substitution expands to auto-<merge-sha> at deploy
time, but the image was pushed under a semver tag (v0.3.0) by Gitea
Actions, so the deploy fails with 'No such image'.
Hardcoding the tag in compose.yml makes the deploy deterministic and
removes the brencher coupling. Bumping the voice-gateway release now
requires updating this string in addition to the tag in
Org1/hermes-voice-gateway.
Bump sequence:
1. Push tag v0.4.0 in Org1/hermes-voice-gateway -> workflow builds image
2. Update this string to v0.4.0
3. brencher deploys
`hermes proxy` subcommands are start/status/providers, not run. The
`proxy run` form was based on an outdated skill summary; the actual
argparse rejects 'run' as an invalid choice and the container exits
with code 2 before the aiohttp proxy binds to :8645.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Two new services in the
hermes_infrastack:hermes-proxy— OpenAI-compatible HTTP egress on :8645. Shares the same OAuth credentials as the gateway viahermes_gateway_datavolume. Reachable only via thehermes_proxyoverlay (internal: true).voice-gateway— Python aiohttp WS bridge between browser and hermes-proxy. Placementnode.hostname==rudolf-T. Image is built externally by Gitea Actions inOrg1/hermes-voice-gateway(workflowrelease.ymlon tag push) and pulled fromgitea.rudolf.keenetic.link/hermes/hermes-voice-gateway.Piper voice model is downloaded on first start via
entrypoint.shfrom HuggingFace.History
0054d9c— initial: add hermes-proxy + voice-gateway to hermes_infra stackc55a40b— fix: drop shell default syntax from HERMES_PROXY_TOKEN24ede4a— fix: drop HERMES_PROXY_TOKEN env (auth skipped for MVP)c2f1b06— fix: hardcode voice-gateway image tag to v0.3.0 (brencher's${version}substitution emitsauto-<sha>tags that don't exist)f9f2253— fix: correct hermes-proxy command (proxy start, notproxy run— the actual argparse rejectsrunas invalid choice)Verification
docker stack deploy -c hermes_squid/stack-compose.yml hermes_infrasucceedshermes_infra_hermes-proxytask running, listening on :8645hermes_infra_voice-gatewaytask running on rudolf-Tcurl http://rudolf-T:8765/healthzreturns{"status":"ok"}Related
brencher parses ${VAR} via re.sub on the literal token name. ${HERMES_PROXY_TOKEN:-} collapses to the token 'HERMES_PROXY_TOKEN:-' which is not in the env dict, raising KeyError at deploy step. Plain ${HERMES_PROXY_TOKEN} resolves to empty string when the env is unset, which is what the shell default was protecting against.hermes-proxy listens on hermes_proxy overlay which is internal:true — no external ingress. Auth between voice-gateway and hermes-proxy is not required for MVP, and brencher was rejecting the ${HERMES_PROXY_TOKEN} substitution as missing key. Removing the line lets brencher apply the compose; the gateway already connects unauthenticated when the env is absent.brencher's ${version} substitution expands to auto-<merge-sha> at deploy time, but the image was pushed under a semver tag (v0.3.0) by Gitea Actions, so the deploy fails with 'No such image'. Hardcoding the tag in compose.yml makes the deploy deterministic and removes the brencher coupling. Bumping the voice-gateway release now requires updating this string in addition to the tag in Org1/hermes-voice-gateway. Bump sequence: 1. Push tag v0.4.0 in Org1/hermes-voice-gateway -> workflow builds image 2. Update this string to v0.4.0 3. brencher deploysPull request closed