Configure Caddy for gRPC-Web support #3

Closed
opened 2026-03-12 09:55:43 +01:00 by shahondin1624 · 1 comment

Milestone: Infrastructure & Setup

Update the existing Caddy config in llm-multiverse (or document a companion Caddyfile) to handle gRPC-Web translation — add Content-Type mapping, CORS headers, and the grpc_web directive so the browser can call the Orchestrator.

Acceptance Criteria

  • Caddyfile with gRPC-Web reverse proxy configuration
  • CORS headers configured for local dev and production origins
  • Content-Type mapping for gRPC-Web ↔ gRPC translation
  • grpc_web directive enabled
  • Documented how to run Caddy alongside the orchestrator
  • Browser can successfully call the Orchestrator through Caddy
## Milestone: Infrastructure & Setup Update the existing Caddy config in `llm-multiverse` (or document a companion Caddyfile) to handle gRPC-Web translation — add `Content-Type` mapping, CORS headers, and the `grpc_web` directive so the browser can call the Orchestrator. ### Acceptance Criteria - [ ] Caddyfile with gRPC-Web reverse proxy configuration - [ ] CORS headers configured for local dev and production origins - [ ] `Content-Type` mapping for gRPC-Web ↔ gRPC translation - [ ] `grpc_web` directive enabled - [ ] Documented how to run Caddy alongside the orchestrator - [ ] Browser can successfully call the Orchestrator through Caddy
Author
Owner

Implemented and auto-merged via PR #23.

Added Caddyfile with gRPC-Web → gRPC translation, CORS headers, and SvelteKit dev server proxy. All quality gates passed.

Implemented and auto-merged via PR #23. Added Caddyfile with gRPC-Web → gRPC translation, CORS headers, and SvelteKit dev server proxy. All quality gates passed.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: llm-multiverse/llm-multiverse-ui#3