Repository navigation
Expand file tree
/
Copy pathdocker-compose.yml
More file actions
132 lines (117 loc) · 5.44 KB
/
Copy pathdocker-compose.yml
File metadata and controls
132 lines (117 loc) · 5.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
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
# ChatCLI Server - Docker Compose for development
# Usage: docker compose up
services:
chatcli-server:
build:
context: .
dockerfile: Dockerfile
container_name: chatcli-server
ports:
- "50051:50051"
environment:
# Stated explicitly so it always matches the chatcli-home volume below
# (the image's nonroot user has this home).
HOME: /home/nonroot
# Server config
CHATCLI_SERVER_PORT: "50051"
# The published port above only reaches the server if it listens on
# the container's interface. Without this the server binds loopback
# INSIDE the container: the health check still passes (it runs in
# there) while nothing outside can connect.
CHATCLI_BIND_ADDRESS: "${CHATCLI_BIND_ADDRESS:-0.0.0.0}"
# REQUIRED with the bind above: a server reachable from outside the
# container with no credential admits every caller as an
# administrator, so it refuses to start and says so. Compose cannot
# express "required unless loopback", so the check lives in the
# server. To run without a token, keep it inside the container:
# CHATCLI_BIND_ADDRESS=127.0.0.1 (then use `docker exec`)
CHATCLI_SERVER_TOKEN: "${CHATCLI_SERVER_TOKEN:-}"
# Per-user JWTs instead of (or alongside) the shared token.
# HS256 secret, or an RS256 public key (PEM) via CHATCLI_JWT_PUBLIC_KEY.
CHATCLI_JWT_SECRET: "${CHATCLI_JWT_SECRET:-}"
CHATCLI_JWT_PUBLIC_KEY: "${CHATCLI_JWT_PUBLIC_KEY:-}"
CHATCLI_JWT_ISSUER: "${CHATCLI_JWT_ISSUER:-}"
CHATCLI_JWT_AUDIENCE: "${CHATCLI_JWT_AUDIENCE:-}"
# LLM Provider (configure at least one)
LLM_PROVIDER: "${LLM_PROVIDER:-}"
LLM_MODEL: "${LLM_MODEL:-}"
OPENAI_API_KEY: "${OPENAI_API_KEY:-}"
OPENAI_MODEL: "${OPENAI_MODEL:-}"
ANTHROPIC_API_KEY: "${ANTHROPIC_API_KEY:-}"
ANTHROPIC_MODEL: "${ANTHROPIC_MODEL:-}"
GOOGLEAI_API_KEY: "${GOOGLEAI_API_KEY:-}"
GOOGLEAI_MODEL: "${GOOGLEAI_MODEL:-}"
XAI_API_KEY: "${XAI_API_KEY:-}"
XAI_MODEL: "${XAI_MODEL:-}"
ZAI_API_KEY: "${ZAI_API_KEY:-}"
ZAI_MODEL: "${ZAI_MODEL:-}"
MINIMAX_API_KEY: "${MINIMAX_API_KEY:-}"
MINIMAX_MODEL: "${MINIMAX_MODEL:-}"
MINIMAX_API_COMPAT: "${MINIMAX_API_COMPAT:-}"
MOONSHOT_API_KEY: "${MOONSHOT_API_KEY:-}"
MOONSHOT_MODEL: "${MOONSHOT_MODEL:-}"
OPENROUTER_API_KEY: "${OPENROUTER_API_KEY:-}"
OPENROUTER_MODEL: "${OPENROUTER_MODEL:-}"
OLLAMA_ENABLED: "${OLLAMA_ENABLED:-}"
OLLAMA_BASE_URL: "${OLLAMA_BASE_URL:-}"
OLLAMA_MODEL: "${OLLAMA_MODEL:-}"
# AWS Bedrock (static keys; prefer an instance role or SSO on real hosts)
AWS_ACCESS_KEY_ID: "${AWS_ACCESS_KEY_ID:-}"
AWS_SECRET_ACCESS_KEY: "${AWS_SECRET_ACCESS_KEY:-}"
AWS_SESSION_TOKEN: "${AWS_SESSION_TOKEN:-}"
BEDROCK_REGION: "${BEDROCK_REGION:-}"
BEDROCK_MODEL: "${BEDROCK_MODEL:-}"
# StackSpot
CLIENT_ID: "${CLIENT_ID:-}"
CLIENT_KEY: "${CLIENT_KEY:-}"
STACKSPOT_REALM: "${STACKSPOT_REALM:-}"
STACKSPOT_AGENT_ID: "${STACKSPOT_AGENT_ID:-}"
# GitHub Copilot
GITHUB_COPILOT_TOKEN: "${GITHUB_COPILOT_TOKEN:-}"
COPILOT_MODEL: "${COPILOT_MODEL:-}"
# Corporate CA bundle for every outbound TLS connection (PEM path inside the container)
CHATCLI_CA_BUNDLE: "${CHATCLI_CA_BUNDLE:-}"
# Provider fallback chain (comma-separated, e.g. "OPENAI,CLAUDEAI,GOOGLEAI").
# A non-empty list is what turns the chain on; there is no separate
# enable switch. CHATCLI_FALLBACK_MODEL_<PROVIDER> picks the model per
# provider (default: the server model).
CHATCLI_FALLBACK_PROVIDERS: "${CHATCLI_FALLBACK_PROVIDERS:-}"
CHATCLI_FALLBACK_MAX_RETRIES: "${CHATCLI_FALLBACK_MAX_RETRIES:-2}"
CHATCLI_FALLBACK_COOLDOWN_BASE: "${CHATCLI_FALLBACK_COOLDOWN_BASE:-30s}"
CHATCLI_FALLBACK_COOLDOWN_MAX: "${CHATCLI_FALLBACK_COOLDOWN_MAX:-5m}"
# MCP (Model Context Protocol)
CHATCLI_MCP_ENABLED: "${CHATCLI_MCP_ENABLED:-}"
CHATCLI_MCP_CONFIG: "${CHATCLI_MCP_CONFIG:-}"
# Memory and bootstrap
CHATCLI_MEMORY_ENABLED: "${CHATCLI_MEMORY_ENABLED:-}"
CHATCLI_BOOTSTRAP_ENABLED: "${CHATCLI_BOOTSTRAP_ENABLED:-}"
# Logging
LOG_LEVEL: "${LOG_LEVEL:-info}"
volumes:
# The image runs as the distroless "nonroot" user (uid 65532) with
# HOME=/home/nonroot, and the root filesystem is read-only, so the
# whole home is one named volume: ~/.chatcli (sessions, memory,
# plugins, logs) lives in it and survives restarts. It is mounted at
# the image's own home because Docker seeds a new named volume with the
# ownership of the directory it covers; a volume over a path the image
# lacks (such as /home/chatcli/...) would be root-owned and unwritable.
# Drop plugin binaries into ~/.chatcli/plugins inside this volume.
- chatcli-home:/home/nonroot
restart: unless-stopped
# The image HEALTHCHECK runs `chatcli healthcheck`, which reads the same
# CHATCLI_SERVER_PORT and CHATCLI_SERVER_TLS_CERT as the server, so it
# follows TLS on its own. With mutual TLS (CHATCLI_SERVER_TLS_CLIENT_CA)
# also set CHATCLI_TLS_CLIENT_CERT and CHATCLI_TLS_CLIENT_KEY, the client
# pair chatcli connect uses.
read_only: true
tmpfs:
- /tmp:size=100M
security_opt:
- no-new-privileges:true
deploy:
resources:
limits:
cpus: "2.0"
memory: 1G
volumes:
chatcli-home: