Hermes Agent custom image with Ollama Cloud config for Railway
Find a file
Felipe Domingues 1740e05917
Add Mika runtime bridge to Hermes image (#2)
* Add Mika runtime bridge to Hermes image

* Build canary image tags on branch pushes
2026-04-30 20:41:07 -03:00
.github/workflows Add Mika runtime bridge to Hermes image (#2) 2026-04-30 20:41:07 -03:00
patches Add Mika runtime bridge to Hermes image (#2) 2026-04-30 20:41:07 -03:00
plugins/mika_runtime Add Mika runtime bridge to Hermes image (#2) 2026-04-30 20:41:07 -03:00
Dockerfile Add Mika runtime bridge to Hermes image (#2) 2026-04-30 20:41:07 -03:00
entrypoint.sh Add Mika runtime bridge to Hermes image (#2) 2026-04-30 20:41:07 -03:00
README.md Add Dockerfile with Ollama Cloud config for Railway deploy 2026-04-24 18:37:52 -03:00

Hermes Agent - Ollama Cloud Custom Image

Custom Docker image for deploying Hermes Agent on Railway with Ollama Cloud provider and Gemma 4 31B model.

Why this exists

The Hermes gateway ignores environment variables for the primary model configuration and only reads from config.yaml. This image bakes the correct config at build time, solving the fallback to anthropic/claude-opus-4.6 issue.

Configuration

The image pre-configures:

  • Provider: ollama-cloud
  • Model: gemma4:31b-cloud
  • Config path: /opt/data/.hermes/config.yaml

Environment Variables (set in Railway)

HERMES_HOME=/opt/data/.hermes
API_SERVER_ENABLED=true
API_SERVER_KEY=your-secure-key
GATEWAY_ALLOW_ALL_USERS=false
HERMES_SOUL_OVERRIDE=Your custom soul prompt here
HERMES_STT_PROVIDER=local
HERMES_TTS_PROVIDER=disabled
OLLAMA_API_KEY=your-ollama-api-key
PORT=8642
TELEGRAM_BOT_TOKEN=your-bot-token
TELEGRAM_ALLOWED_USERS=your-user-id
TELEGRAM_HOME_CHANNEL=your-channel-id

Deploy to Railway

  1. Connect this GitHub repo to Railway
  2. Railway auto-detects the Dockerfile
  3. Add the environment variables above
  4. Deploy

License

MIT