Stack templates

Edit the compose templates used by the New agent flow. Overrides live at /data/stack-templates/<name>.yml.j2 and survive deploys. Existing stacks aren't changed retroactively — overrides apply the next time a stack is created. Any ${VAR} declared here surfaces as a field on every person's Settings page, bucketed by name pattern.

hermes.yml.j2

Rendering from built-in.

services:
  hermes:
    image: hermes-cs:latest
    container_name: {{ name }}
    restart: unless-stopped
    # Symlink the m365 dotfiles into /root before launching Hermes.
    # Direct file bind-mounts fail with "not a directory" when the destination
    # paths don't pre-exist in the image (a runc MS_REC quirk).
    entrypoint: ["/usr/bin/tini", "-g", "--", "/bin/sh", "-lc"]
    command:
      - >-
        ln -sf /root/m365/.cli-m365-all-connections.json /root/.cli-m365-all-connections.json
        && ln -sf /root/m365/.cli-m365-connection.json /root/.cli-m365-connection.json
        && ln -sf /root/m365/.cli-m365-msal.json /root/.cli-m365-msal.json
        && ln -sf /opt/data/m365/.cli-m365-all-connections.json /opt/data/.cli-m365-all-connections.json
        && ln -sf /opt/data/m365/.cli-m365-connection.json /opt/data/.cli-m365-connection.json
        && ln -sf /opt/data/m365/.cli-m365-msal.json /opt/data/.cli-m365-msal.json
        && mkdir -p /opt/data/home /opt/data/home/.config
        && ln -sf /opt/data/m365/.cli-m365-all-connections.json /opt/data/home/.cli-m365-all-connections.json
        && ln -sf /opt/data/m365/.cli-m365-connection.json /opt/data/home/.cli-m365-connection.json
        && ln -sf /opt/data/m365/.cli-m365-msal.json /opt/data/home/.cli-m365-msal.json
        && ln -sf /opt/data/m365/.cli-m365-all-connections.json /opt/hermes/.cli-m365-all-connections.json
        && ln -sf /opt/data/m365/.cli-m365-connection.json /opt/hermes/.cli-m365-connection.json
        && ln -sf /opt/data/m365/.cli-m365-msal.json /opt/hermes/.cli-m365-msal.json
        && mkdir -p /opt/hermes/.config
        && chown -R hermes:hermes /opt/hermes/.config
        && exec /opt/hermes/docker/entrypoint.sh /opt/hermes/.venv/bin/hermes gateway run
    user: "0:0"
    env_file:
      - .env
    ports:
      - "{{ gateway_port | default(8643) }}:8642"
    volumes:
      - ./hermes:/opt/data
      - ./gws:/root/.config/gws
      - ./m365:/root/m365
      - ./m365:/opt/data/m365
      - /data/_people:/data/_people
    networks:
      - hermes-net
    environment:
      - PATH=/opt/hermes/.venv/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
      - HERMES_ALLOW_ROOT_GATEWAY=1
      - ANTHROPIC_API_KEY=${ANTHROPIC_API_KEY:-}
      - OPENAI_API_KEY=${OPENAI_API_KEY:-}
      - OPENROUTER_API_KEY=${OPENROUTER_API_KEY:-}
      - TELEGRAM_BOT_TOKEN=${TELEGRAM_BOT_TOKEN:-}
      - TELEGRAM_ALLOWED_USERS=${TELEGRAM_ALLOWED_USERS:-}
      - TELEGRAM_HOME_CHANNEL=${TELEGRAM_HOME_CHANNEL:-}
      - TELEGRAM_HOME_CHANNEL_NAME=${TELEGRAM_HOME_CHANNEL_NAME:-}
    deploy:
      resources:
        limits:
          memory: 4G
          cpus: "{{ cpu_limit | default('1.0') }}"
networks:
  hermes-net:
    driver: bridge

—

Env vars exposed by this template

Detected from ${VAR} refs in the compose above. Each becomes a field on every person's Settings page, auto-bucketed by name pattern (*_API_KEY → API keys · HERMES_* → Hermes · TELEGRAM_* → Telegram · else → Nanobot).

—

Stack templates

hermes.yml.j2

Env vars exposed by this template

Working…