dank/serverAppConfigs
1
0
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

feat(hermes-webui): publish webui on LAN interface instead of loopback

Browse Source 
LAN clients now connect directly to 192.168.0.143:8787 (password-gated via
HERMES_WEBUI_PASSWORD); the SSH tunnel via port 22 remains the sole
off-network ingress. Recreation also re-reads the rotated password from
dankclaw/.env via the [Container] EnvironmentFile.
This commit is contained in:
Frank
2026-08-31 13:13:07 -07:00
parent ba0345ae7a
commit 44438979b3
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
dankclaw/hermes/quadlet/hermes-webui.container
+5 -4
View File
@@ -7,9 +7,10 @@
# foreground mode: bootstrap.py creates .venv inside the mounted checkout,
# installs WebUI + agent deps, then execs server.py as a single foreground
# process. It reads HERMES_HOME=/data, so it drives the SAME agent state
# (memory, skills, sessions) as the gateway container. Loopback-only publish:
# the SSH tunnel (phone -> Dankclaw:22) is the sole ingress. The password
# gates Hermex logins and lives in the host .env (git-ignored).
# (memory, skills, sessions) as the gateway container. Published on the LAN
# interface only (192.168.0.143:8787): password-gated (HERMES_WEBUI_PASSWORD
# in the host .env, git-ignored), so LAN clients connect directly and the
# SSH tunnel (phone -> Dankclaw:22) remains the sole off-network ingress.
[Unit]
Description=Hermes webui (Hermex) container
@@ -29,7 +30,7 @@ Environment=HERMES_WEBUI_PASSWORD=${HERMES_WEBUI_PASSWORD}
Environment=HERMES_WEBUI_SKIP_ONBOARDING=1
Volume=/home/dank/hermes-data:/data
Volume=/home/dank/hermes-webui:/webui
PublishPort=127.0.0.1:8787:8787
PublishPort=192.168.0.143:8787:8787
Exec=python3 /webui/bootstrap.py --foreground
# JSON exec form on purpose: this quadlet generator joins a bare HealthCmd
# into ONE argv element with \x20 escapes and then shell-executes it — the