Self-host templates without Caddy

Agreed making caddy basically the only option is a bad idea imo, sure it leads to less "headaches" when it comes to issues with self-hosting having it all focused on one single stack as you don't have to constantly try it out between different web servers and how they might just handle stuff slightly different, but I myself also mainly use NGINX as a reverse-proxy via npmplus for all my applications and obviously there are many more that use just NGINX by itself or Traefik

The problem in particular is how absolutely crazily intertwined Caddy is into this stack. It isn't just added next to Fluxer, or on top of it, so you can just remove it and replace the one env. variable that calls for it. Nope, aside from Caddy itself being a part of the stack which is removable, there are multiple calls directly to Caddy from other parts of the stack. Looking at the Caddy file, you can adapt it to NGINX proxy templates, that isn't a huge deal in and of itself. The major issue is that the stack basically expects Caddy to be present, and I have no idea what will happen if you just rip it out.