mirror of
https://github.com/domfelipe/hermes-agent-custom.git
synced 2026-08-07 09:16:41 +00:00
fix: start hermes gateway for telegram runtime
This commit is contained in:
parent
7718920777
commit
2d48a02271
2 changed files with 63 additions and 2 deletions
|
|
@ -24,6 +24,7 @@ GATEWAY_ALLOW_ALL_USERS=false
|
|||
HERMES_SOUL_OVERRIDE=Your custom soul prompt here
|
||||
HERMES_STT_PROVIDER=local
|
||||
HERMES_TTS_PROVIDER=disabled
|
||||
HERMES_GATEWAY_ENABLED=auto
|
||||
OLLAMA_API_KEY=your-ollama-api-key
|
||||
PORT=8642
|
||||
TELEGRAM_BOT_TOKEN=your-bot-token
|
||||
|
|
@ -40,6 +41,10 @@ MIKA_INTERNAL_FUNCTION_SECRET=shared-internal-secret
|
|||
`MIKA_PLATFORM_FUNCTIONS_BASE_URL` or `SUPABASE_URL` is present. The Mika
|
||||
platform provisions all of these automatically for managed Railway services.
|
||||
|
||||
`HERMES_GATEWAY_ENABLED=auto` starts `hermes gateway run` whenever
|
||||
`TELEGRAM_BOT_TOKEN` is present, so the container consumes Telegram polling in
|
||||
addition to serving the dashboard/proxy runtime API.
|
||||
|
||||
## Validation
|
||||
|
||||
```bash
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue