Files
computer-playbook/roles/web-app-flowise/meta/volumes.yml
kevinveenbirkenbachandClaude Opus 4.8 703380fba7 refactor(web-app-flowise): consume the shared gateway instead of a private sidecar
Flowise shipped its own LiteLLM container: own image, own port, own
config template, own volume, own master key. Every further consumer of
the model plane would have needed the same again.

The service entry becomes a plain consumer flag on svc-ai-litellm, so the
include resolver pulls the gateway into the round and the flag is false
when no gateway is deployed. The sidecar render task, its template, its
volume and the compose_handlers_flush dance that existed only to sequence
that render are all gone; 00_core.yml is back to the standard shape.

Two corrections ride along in env.j2. The endpoint keeps its /v1 suffix,
which the OpenAI-compatible surface requires. And Flowise now presents
its own virtual key from credentials.litellm_api_key rather than the
gateway master key, which previously handed a consumer full
administrative access to the gateway.

The whole block is conditional now, so without a gateway Flowise renders
no OPENAI_API_BASE at all instead of an address pointing nowhere.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-25 19:03:30 +02:00

7 lines
95 B
YAML

---
flowise_data:
type: volume
mounts:
- service: flowise
target: /root/.flowise