llm-multiverse/llm-multiverse
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

feat: configure Caddy v2 edge proxy (#92) #197

Merged
shahondin1624 merged 1 commits from feature/issue-92-caddy-proxy into main 2026-03-11 10:43:17 +01:00
Conversation 0 Commits 1 Files Changed 4 +101 -3
shahondin1624 commented 2026-03-11 10:43:12 +01:00
Owner
Copy Link

Summary

  • Caddyfile with reverse proxy to orchestrator via h2c (gRPC)
  • Self-signed TLS for local dev, automatic Let's Encrypt for production
  • /healthz endpoint for monitoring
  • Internal services no longer exposed directly (orchestrator port removed)
  • Caddy data/config volumes for TLS certificate persistence

Configuration

  • DOMAIN env var: set to your domain for Let's Encrypt (default: localhost)
  • TLS_MODE env var: internal for self-signed (default), omit for Let's Encrypt
  • Ports 80/443 exposed via HTTP_PORT/HTTPS_PORT env vars

Test Plan

  • docker compose config validates successfully
  • Caddyfile syntax is valid

Closes #92

## Summary - Caddyfile with reverse proxy to orchestrator via h2c (gRPC) - Self-signed TLS for local dev, automatic Let's Encrypt for production - /healthz endpoint for monitoring - Internal services no longer exposed directly (orchestrator port removed) - Caddy data/config volumes for TLS certificate persistence ## Configuration - `DOMAIN` env var: set to your domain for Let's Encrypt (default: `localhost`) - `TLS_MODE` env var: `internal` for self-signed (default), omit for Let's Encrypt - Ports 80/443 exposed via `HTTP_PORT`/`HTTPS_PORT` env vars ## Test Plan - [x] `docker compose config` validates successfully - [x] Caddyfile syntax is valid Closes #92
shahondin1624 added 1 commit 2026-03-11 10:43:13 +01:00
feat: configure Caddy v2 edge proxy (issue #92) 77ef1b1174 
Add Caddy reverse proxy with self-signed TLS for local dev and
automatic Let's Encrypt for production domains. Routes all external
traffic through Caddy to the orchestrator via h2c. Internal services
are no longer exposed directly. Includes /healthz endpoint.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
shahondin1624 merged commit a55ed3d8ff into main 2026-03-11 10:43:17 +01:00
shahondin1624 deleted branch feature/issue-92-caddy-proxy 2026-03-11 10:43:17 +01:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
cat:agent
Agent related
 cat:cross-cutting
Cross-cutting concern
 cat:deployment
Deployment related
 cat:devops
DevOps related
 cat:performance
Performance related
 cat:security
Security related
 cat:tech-debt
Technical debt from code reviews
 lang:protobuf
Protocol Buffers
 lang:python
Python language
 lang:rust
Rust language
 priority:critical
Critical priority
 priority:high
High priority
 priority:low
Low priority
 priority:medium
Medium priority
 service:audit
Audit service
 service:memory
Memory service
 service:model-gateway
Model Gateway service
 service:orchestrator
Orchestrator service
 service:search
Search service
 service:secrets
Secrets service
 service:tool-broker
Tool Broker service
 type:bug
Bug fix
 type:documentation
Docs
 type:feature
New functionality
 type:infrastructure
Build tooling, project setup
 type:refactor
Restructuring
 type:research
Investigation, benchmarking
 type:testing
Tests
 workflow:blocked
Blocked after max retries
 workflow:manual
Requires manual intervention — blocked from auto-dev
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
shahondin1624
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: llm-multiverse/llm-multiverse#197
Delete Branch "feature/issue-92-caddy-proxy"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?