fix: the clinical MCP has a name that says what it is; gateway from the vault
Some checks failed
Forgejo Android APK / Root app tests (push) Successful in 52s
Forgejo Docker Build / Root app tests (push) Successful in 47s
Forgejo Android APK / Build signed APK (push) Successful in 2m14s
Forgejo Docker Build / Build Docker image (push) Successful in 18s
Forgejo Docker Build / Deploy to the host (push) Failing after 0s
Some checks failed
Forgejo Android APK / Root app tests (push) Successful in 52s
Forgejo Docker Build / Root app tests (push) Successful in 47s
Forgejo Android APK / Build signed APK (push) Successful in 2m14s
Forgejo Docker Build / Build Docker image (push) Successful in 18s
Forgejo Docker Build / Deploy to the host (push) Failing after 0s
"mcp" said nothing — this host runs several MCP servers. The clinical corpus query service now also answers to clinical-mcp, and ped-ai asks for it by that name. The bare service name stays an alias automatically, so anything still pointing at http://mcp:8000 keeps working. Hyphens rather than underscores: underscores are legal in Docker's embedded DNS but not in hostnames generally. LITELLM_API_BASE goes back to being unset here, so OpenBao's https://llm.danvics.com applies. The public hostname is the deliberate choice for consistency across the estate. It is not a speed question — the gateway hop is ~19ms on calls taking hundreds of milliseconds, and describing that as "4x" was a misleading way to put it. The real cost is that AI calls now depend on Caddy, public DNS and edge TLS; one line here pins it back to the container network. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Dv6sqaY6Vq3ChZHMem3cnU
This commit is contained in:
parent
a3dee83ac2
commit
85dbbc1a4a
1 changed files with 9 additions and 12 deletions
|
|
@ -14,20 +14,17 @@ services:
|
|||
env_file:
|
||||
- .env
|
||||
environment:
|
||||
CLINICAL_ASSISTANT_MCP_URL: http://mcp:8000/mcp
|
||||
# clinical-mcp, not mcp: this host runs several MCP servers and the bare
|
||||
# name said nothing about which. Same container, added alias.
|
||||
CLINICAL_ASSISTANT_MCP_URL: http://clinical-mcp:8000/mcp
|
||||
REDIS_URL: redis://ped-ai-redis:6379
|
||||
LOKI_URL: http://monitoring-loki:3100
|
||||
# Deliberate: ped-ai talks to LiteLLM over the container network, not the
|
||||
# public hostname. Clinical traffic then never leaves the host and does
|
||||
# not depend on Caddy, public DNS or edge TLS being up. The latency
|
||||
# difference is ~19ms on calls that take hundreds of ms, so speed is not
|
||||
# the reason — not leaving the box is.
|
||||
#
|
||||
# OpenBao still stores https://llm.danvics.com for this key and Compose
|
||||
# env wins, so the vault value is dead. Change it in the vault to match,
|
||||
# or this line will keep looking like the accidental override it used to
|
||||
# be. The app's AppRole is read-only, so that has to be done by hand.
|
||||
LITELLM_API_BASE: http://litellm:4000
|
||||
# LITELLM_API_BASE is intentionally not set here: OpenBao supplies
|
||||
# https://llm.danvics.com and Compose env would override it. The public
|
||||
# hostname is the deliberate choice for consistency across the estate.
|
||||
# The cost is not speed (~19ms on calls taking hundreds) — it is that
|
||||
# AI calls now depend on Caddy, public DNS and edge TLS being up.
|
||||
# To pin ped-ai to the container network instead, set it here.
|
||||
TTS_PROVIDER: litellm
|
||||
LITELLM_TTS_MODEL: local-kokoro-tts
|
||||
LITELLM_TTS_VOICE: sherpa/kokoro:am_adam
|
||||
|
|
|
|||
Loading…
Reference in a new issue