Edit history
Earlier versions of Self-host templates without Caddy, newest first.
Current version | Edited by Rex
Changes
Remove Caddy, or keep Caddy as a template option and create a new template without Caddy (reverse-proxy neutral)Removed: ### ChecksRemoved: Removed: - ☑ I searched existing issues.Removed: - ☑ I wrote this report in my own words, except for direct translation if needed.Removed:
Show
Self-host templates without Caddy
Original by Rex
Show
Self-host templates without Caddy
What needs fixing?
Good afternoon dear Fluxer Team, Caddy, or Traefik, are in my opinion a blight on the infrastructure. Many systems are already in place (almost always without Caddy/Traefik), and I would like to use a server I already own and have setup infrastructure on (pure NGINX in this case), rather than having to buy a completely new server just for Fluxer, as Fluxer's current setup would overwrite my entire network stack. Your current documentation and template is basically intertwined with Caddy and nearly impossible to remove without major issues. The problem is that most people do not necessarily use Caddy (or Traefik for that matter), and so if you'd be so kind as to write reverse-proxy neutral Docker templates, that would be really helpful. Because when you do, everyone can use whichever one they like, be it Caddy, Traefik, NPM, pure NGINX, etc. Best regards,Location
https://docs.fluxer.app/operator/get-started/#step-2-download-the-stackSuggested change
Remove Caddy, or keep Caddy as a template option and create a new template without Caddy (reverse-proxy neutral)Checks
- ☑ I searched existing issues.
- ☑ I wrote this report in my own words, except for direct translation if needed.