Evenfire is an intelligence layer platform for running LLM agents that take real actions, on your infrastructure
TypeScript
docs: update docs for dev-mode docker compose
Jose Gabriel Ramirez Encinas8fcc255ea4bd
diff --git a/docs/get-started/dev-mode.md b/docs/get-started/dev-mode.mdindex 5d0a4d6f2..85a69a07c 100644--- a/docs/get-started/dev-mode.md+++ b/docs/get-started/dev-mode.md@@ -148,8 +148,18 @@ docker run --rm -p 127.0.0.1:8080:8080 \mcp-host-dev```-The root `docker-compose.yml` declares the same dev-mode settings, plus an-optional channel-reader under the `telegram` profile. Its mcp-host build does-not work as written: it uses `context: ./mcp-host`, so the Dockerfile cannot-find `packages/`. It also publishes `8080:8080` on all interfaces with auth-off. Use the commands above instead.+The root `docker-compose.yml` runs the same setup. It builds mcp-host from the+repository root, publishes the port on `127.0.0.1:8080` only, and passes+through `CLERUM_MODEL_PROVIDER` and the `OPENAI_API_KEY`, `CLAUDE_API_KEY`,+`ZAI_API_KEY` and `BAILIAN_API_KEY` keys from your shell:++```bash+# from the repository root+OPENAI_API_KEY=sk-... docker compose up mcp-host+```++It also has an optional channel-reader under the `telegram` profile+(`docker compose --profile telegram up`), already pointed at mcp-host with+`CLERUM_HOST_REF=dev-host`. Set `CLERUM_TELEGRAM_BOT_TOKEN` and+`TELEGRAM_ALLOWED_USER_ID` (your Telegram user ID) first, and edit its+`CLERUM_CHANNEL` if your bot setup differs.