The web server deployment model breaks at hobby scale

Post by mikepavone » Fri, Aug 07, 2026, 3:57 PM UTC

tingletech wrote: post #18

bradly wrote: post #5

I'm not sure I understand this post. Is this talking about self hosting Caddy in a home lab setting or just static web hosting on a VPS?

I think the author is distributing a web app that is run by hobbyists with a lot of esoteric home labs?

Post by sam_lowry_ » Fri, Aug 07, 2026, 4:04 PM UTC

josephg wrote: post #26

sam_lowry_ wrote: post #7

Earlier quoted context omitted.

I think the author missed the root cause, which is the demise of (unencrypted) HTTP/1.1 connections.

I'm glad unencrypted http/1.1 was deprecated. I want a privacy online. TLS also gives you much better data integrity guarantees. Some ISPs - particularly in the US - actively inject javascript code into websites served over plain HTTP. I just wish nginx / caddy / etc had better out-of-the-box support for letsencrypt. It would be way easier to set up if it was just built in to nginx. Let me specify my domain in my ngi…

Post by sam_lowry_ » Fri, Aug 07, 2026, 4:21 PM UTC

crtasm wrote: post #40

smw wrote: post #29

Earlier quoted context omitted.

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} } }

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

Post by glaslong » Fri, Aug 07, 2026, 4:27 PM UTC

lee_ars wrote: post #49

glaslong wrote: post #47

Earlier quoted context omitted.

They're not all tooootally atomic, I have clustered things like libation+audiobookshelf, ollama+ds4+litellm, but I like that I can manage things almost entirely at the network and host level, generally atomically per service, and especially between services (eg homeassistant and the local ai). It's DEFINITIVELY overkill, and fills up fast, but nix making everything near fully declarative to roll fwd/back or shuffle b…

Sounds like a poster child for LXC containerization with Proxmox — all the host-level management of a non-ephemeral VM (including snapshots!), without the every-machine-has-its-own-kernel overhead.

Post by [deleted] » Fri, Aug 07, 2026, 4:38 PM UTC

smw wrote: post #29

AussieWog93 wrote: post #11

Earlier quoted context omitted.

Honestly, this is a problem that has been solved by LLMs. Just point Claude Code to the server over SSH and say "We need Immich to be served over HTTPS". 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.

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} } }