Files
hermes-ui/docker-compose.yml
T
toor c93e1fe1bd
Build / build (push) Canceled after 0s
NPM Lockfile Check / npm ci --ignore-scripts (push) Canceled after 0s
Playwright / e2e (push) Canceled after 0s
Phase 002: rebrand to hermes-ui and consolidate i18n to zh/en
Removes the ekko / hermes-web-ui branding from the whole tree and drops
eight locale files, so the project presents one name and one language pair.

Data compatibility is deliberate, not accidental: DB filenames, the JWT
audience, and skill manifest ownership all still recognise their pre-rename
values so existing deployments under ~/.hermes-web-ui keep working without a
re-login or a re-injection.

scripts/harness-check.mjs now scans for the legacy strings and fails the
build on any new occurrence, with an explicit allow-list (and reasons) for
the compatibility paths that must keep them.
2026-10-16 11:11:29 +08:00

27 lines
979 B
YAML

services:
hermes-ui:
build:
context: .
dockerfile: Dockerfile
image: ${WEBUI_IMAGE:-hermes-ui-local:latest}
container_name: ${WEBUI_CONTAINER_NAME:-hermes-ui}
ports:
- "${PORT:-6060}:${PORT:-6060}"
- "${PREVIEW_FRONTEND_PORT:-8651}:8651"
- "${XAI_OAUTH_PORT:-56121}:56121"
volumes:
- ${HERMES_DATA_DIR:-./hermes_data}:/home/agent/.hermes
- ${HERMES_DATA_DIR:-./hermes_data}/hermes-ui:/home/agent/.hermes-web-ui
environment:
- PORT=${PORT:-6060}
- HERMES_HOME=/home/agent/.hermes
- HERMES_BIN=/opt/hermes/.venv/bin/hermes
- HERMES_WEB_UI_MANAGED_GATEWAY=1
- HERMES_WEB_UI_AUTH_JWT_EXPIRES_IN=${HERMES_WEB_UI_AUTH_JWT_EXPIRES_IN:-30d}
- HERMES_WEB_UI_XAI_CALLBACK_BIND_HOST=0.0.0.0
- PATH=/opt/hermes/.venv/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
- HERMES_ALLOW_ROOT_GATEWAY=1
restart: unless-stopped
stdin_open: true
tty: true