Re:The web server deployment model breaks at hobby scale
by smw on Friday August 07, 2026 @10:42AM
(#49211227)
Here's the entirety of the Caddy config to reverse proxy something with managed tls certs. I feel like it's not that big a deal?
photos.example.com {
reverse_proxy 127.0.0.1:8080 {
header_up X-Real-IP {remote_host}
}
}
Re:The web server deployment model breaks at hobby scale
by crtasm on Friday August 07, 2026 @11:00AM
(#49211507)
caddy passes on the source IP by default so it's even easier than that
photos.example.com {
reverse_proxy 127.0.0.1:8080
}
the immich documentation covers this as well as nginx, apache and traefik https://docs.immich.app/administration/reverse-proxy
Re:The web server deployment model breaks at hobby scale
by sam_lowry_ on Friday August 07, 2026 @12:21PM
(#49212787)
Heh... I self-host Immich with Caddy, and it's more complex, really. Caddy runs in podman, there are firewall rules to allow traffic in and out and proper dependencies in systemd units and a readme that covers all that. Exactly the point OP is making.
All because we forced TLS on everyone instead of solving the JS injection problem in some other alternative way. Like... legal, maybe?
You could theoretically upstream the fixed compose.yaml if you felt like it, but the project seemed unusually hostile towards the one fix I tried to upstream.