LLM-Server

Files

T

haylanandClaude-Bot 90ef1a1061 fix(omniroute): keep the gateway published on host port 4000

Not omniroute's own internal port (API_PORT stays at its default 20129,
unreconfigured) - just the Docker port mapping, so existing NPM/firewall
config pointed at :4000 keeps working without changes on that end. New
OMNIROUTE_PORT env var is the host side of "OMNIROUTE_PORT:API_PORT" in
docker-compose.yml's ports: entry.

Also corrected docs/proxy-key-onboarding.md's dashboard-access
instructions - DASHBOARD_PORT was never published to the host in the
first place, so "http://<host>:20128" was never actually reachable as
written; documented reaching it via the container's own bridge-network IP
or an SSH port-forward instead.

llama-server remains unexposed (no ports: entry, only expose:) -
unaffected by this change, confirming it stays that way.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VPZ6TogJiYxG8E4EQBB197

2026-09-03 20:17:08 +02:00

agents

docs(agents): fix tea comment syntax, note map-edit race condition

2026-09-03 19:29:10 +02:00

research

docs(research): LangChain+pgvector-direct vs litellm-pgvector for issue #25

2026-09-02 22:02:58 +02:00

coding-cli-setup.md

fix(omniroute): keep the gateway published on host port 4000

2026-09-03 20:17:08 +02:00

network-access.md

fix(omniroute): keep the gateway published on host port 4000