Repository navigation
Expand file tree
/
Copy pathdocker-compose.yml
More file actions
43 lines (42 loc) · 1.44 KB
/
Copy pathdocker-compose.yml
File metadata and controls
43 lines (42 loc) · 1.44 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
services:
mcp-host:
build:
context: ./mcp-host
dockerfile: Dockerfile
environment:
CLERUM_DEV_MODE: "true"
CLERUM_ENABLE_AUTH: "false"
CLERUM_MODEL_PROVIDER: ${CLERUM_MODEL_PROVIDER:-openai}
OPENAI_API_KEY: ${OPENAI_API_KEY:-}
CLAUDE_API_KEY: ${CLAUDE_API_KEY:-}
ZAI_API_KEY: ${ZAI_API_KEY:-}
BAILIAN_API_KEY: ${BAILIAN_API_KEY:-}
ports:
- "8080:8080"
healthcheck:
test: ["CMD", "wget", "-qO-", "http://localhost:8080/v1/runtime/health"]
interval: 10s
timeout: 5s
retries: 5
start_period: 20s
# channel-reader wires Telegram (or Slack/Email) to mcp-host.
# It requires a real bot token. Omit / comment out this service
# if you only want the local HTTP surface (curl to mcp-host:8080).
channel-reader:
build:
context: ./channel-reader
dockerfile: Dockerfile
depends_on:
mcp-host:
condition: service_healthy
environment:
CLERUM_DEV_MODE: "true"
CLERUM_HOST_REF: dev-host
CLERUM_MCP_HOST_URL: http://mcp-host:8080
# Replace telegram channel/user IDs to match your bot setup.
# "userIds" is the list of Telegram user IDs allowed to send messages.
CLERUM_CHANNEL: >-
{"hostRef":"dev-host","telegram":[{"channelId":"dev-channel","userIds":["${TELEGRAM_ALLOWED_USER_ID:-123456789}"]}]}
CLERUM_TELEGRAM_BOT_TOKEN: ${CLERUM_TELEGRAM_BOT_TOKEN:-}
profiles:
- telegram