mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 10:59:59 +00:00
kevinveenbirkenbachandClaude Opus 4.8
cc4f76ad66
The LiteLLM gateway ships its own admin UI, but svc-ai-litellm stays headless: the UI is optional and public, the gateway is neither. Putting both in one role would either make the UI mandatory or teach the gateway domain logic it has no business knowing. So this role runs no container at all. It loads sys-stk-front-proxy and points domain, http_port and proxy_internal_port at svc-ai-litellm's service entry. The third variable is what makes swarm work: compose reaches the gateway through its published host port, swarm renders the vhost against the internal port and routes over the overlay. networks.local.force_bridge is set because a role without a container has no overlay for openresty to join; the upstream resolves to host.docker.internal and the gateway's published port instead. provides: litellm_ui renames the registry entry, because get_entity_name(web-app-litellm) collides with the key svc-ai-litellm already owns and a duplicate aborts every service resolution repo-wide. The coupling is one-way: the UI role pulls the gateway, the gateway knows nothing about the UI. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
5 lines
66 B
YAML
5 lines
66 B
YAML
---
|
|
canonical:
|
|
litellm: llm.ai.{{ DOMAIN_PRIMARY }}
|
|
aliases: []
|