mirror of
https://github.com/headroomlabs-ai/headroom.git
synced 2026-11-22 13:29:19 +08:00
Headroom's listener speaks plain HTTP, so a shared proxy sent the proxy token, prompts and provider credentials across the network unencrypted unless the operator built their own HTTPS front. docker-compose.https.yml runs Caddy in its own container in front of Headroom: Caddy serves HTTPS and renews the certificate, Headroom's port stays on the compose network, and the proxy token is required. Caddy reaches Headroom by service name, not loopback, so the token is still checked on every request. Assay-Kind: feature Assay-Ask: Teams running Headroom as a shared proxy had no simple way to serve it over HTTPS. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
12 lines
479 B
Caddyfile
12 lines
479 B
Caddyfile
# HTTPS in front of Headroom. Used by docker/docker-compose.https.yml.
|
|
{$HEADROOM_DOMAIN} {
|
|
# Certificate: a public name gets one from Let's Encrypt automatically.
|
|
# For an internal name, uncomment one of these:
|
|
# your company's certificate (mount the files into the caddy service):
|
|
# tls /certs/headroom.crt /certs/headroom.key
|
|
# Caddy's own CA (install its root, /data/caddy/pki/authorities/local/root.crt, on clients):
|
|
# tls internal
|
|
|
|
reverse_proxy headroom:8787
|
|
}
|