Comment history
Versions of a comment on Self-host templates without Caddy, newest first.
Current version | Edited by Rex
Changes
> The caddyfile is simply enough with just basic path based redirections so I'm planning on trying pangolin without caddy.Removed: hey [@shleeable](https://github.com/shleeable) could you share how you did it? i'd love to see it. Added: hey @shleeable could you share how you did it? i'd love to see it. i personally have no issues with caddy being a critical portion of the stack as i understand the limitations you bring up of these solutions, but i think it would be great if the documentation could point to a way that caddy resolves the things it needs like zstd and http3 and just give nginx or any other reverse proxy what it needs to properly communicate with fluxer
Show
the original post seems to be a little aggressive against Caddy... but it look me about 15 seconds to remove the dependency Nginx doesn't support zstd and http3 without a lot of messing around. Caddy doesn't support caching without compiling a module and traefik is overkill in most cases... There isn't a simple middle ground for me.....and a lot of us are throwing cloudflare tunnels or even pangolin in front of this so it's kind of a reverse proxy sandwich. The caddyfile is simply enough with just basic path based redirections so I'm planning on trying pangolin without caddy.hey @shleeable could you share how you did it? i'd love to see it. i personally have no issues with caddy being a critical portion of the stack as i understand the limitations you bring up of these solutions, but i think it would be great if the documentation could point to a way that caddy resolves the things it needs like zstd and http3 and just give nginx or any other reverse proxy what it needs to properly communicate with fluxer
Original by Rex
Show
the original post seems to be a little aggressive against Caddy... but it look me about 15 seconds to remove the dependency Nginx doesn't support zstd and http3 without a lot of messing around. Caddy doesn't support caching without compiling a module and traefik is overkill in most cases... There isn't a simple middle ground for me.....and a lot of us are throwing cloudflare tunnels or even pangolin in front of this so it's kind of a reverse proxy sandwich. The caddyfile is simply enough with just basic path based redirections so I'm planning on trying pangolin without caddy.hey @shleeable could you share how you did it? i'd love to see it. i personally have no issues with caddy being a critical portion of the stack as i understand the limitations you bring up of these solutions, but i think it would be great if the documentation could point to a way that caddy resolves the things it needs like zstd and http3 and just give nginx or any other reverse proxy what it needs to properly communicate with fluxer