I made a little automated Docker reverse proxy called Autocaddy to simplify developing unrelated little trinkets under subdomains of a domain name:
https://github.com/lbfalvy/...
It dispatches subdomains to the (container with the) matching network alias and terminates TLS.

it's a little rough around the edges but to my understanding it shouldn't be an inherent risk (unless you're running things that interfere with name resolution like VPN on the container host, but why would you do that if it's already a container host).

The actual dispatch is like 4 lines, the rest is setting up autotls without either

- forcing the user to build the container and compile Caddy themselves, as would be the case with libdns (I can't believe that's seriously the solution we're marching towards) or

- disregarding a bunch of critical configuration options from Lego because Caddy's lego plugin is garbage, it doesn't actually delegate the task along with config to Lego but also doesn't relay Caddy's own config so ultimately there's no effective way to set propagation delay.

Not sure why I read autoDaddy but nice dude, sounds good!

@Jifuna The name is a play on AutoCAD, for no reason whatsoever other than perhaps that it was in my working memory because some months ago I applied to work with them which required a bit of research about the software.

@lbfalvy haha nice, I should have know