Files
composes/hermes/.env.example
T
tiennm99 82892042dc fix(hermes): configure chat platforms in /opt/data/.env, not Coolify
The gateway's allow-lists read only the profile .env under the default
multiplex mode, so Telegram values passed from the environment left every
user blocked. Drop the passthrough and document the dashboard as the one
place to set them, plus the dashboard secret's 16-byte minimum.
2026-10-05 17:35:34 +07:00

20 lines
667 B
Bash

# Copy to .env and fill in. Never commit .env.
#
# cp .env.example .env
# Full public URL of the dashboard, e.g. https://hermes.example.com.
HERMES_DASHBOARD_PUBLIC_URL=https://hermes.example.com
# Dashboard login. Generate the password with: openssl rand -base64 24
HERMES_DASHBOARD_USERNAME=hermes
HERMES_DASHBOARD_PASSWORD=
# Signs dashboard sessions; keep it stable. Generate with: openssl rand -hex 32
HERMES_DASHBOARD_SECRET=
# Provider keys normally live in /opt/data/.env, set from the dashboard.
# Uncomment here and in compose.yml to pass one from the environment instead.
# OPENROUTER_API_KEY=
# ANTHROPIC_API_KEY=
# OPENAI_API_KEY=
# GOOGLE_API_KEY=