I seem to have nginx, apache and lighthttpd on my NAS. Perhaps time for a cull. Which should survive?
Nginx is the “main” one which is mostly a reverse proxy for containers. Apache is for smokeping. Lighttpd appears to be configured for smokeping too
@jmtd I still find myself defaulting to Apache unless I have a strong reason not to.
@jmtd Neither! Try something new, like Caddy!
algernon ducks and runs
@jmtd I default to nginx these days, if nothing else for the less-annoying-than-apache config syntax.
@noodles I think I've now largely forgotten the intricacies of configuring apache, perhaps a skill I should have kept sharp
@mart_brooks that was what motivated me to move my personal stuff to lighttpd 10 years or so ago: In particular the relative ease of configuring fcgi
So: I've left nginx as Internet-facing, purely reverse proxy; lighttpd was doing some private CGI stuff so I've reconfigured it to be LAN only. Apache it seems was superfluous (pulled in via smokeping, I've since added that to lighttpd)
- replies
- 0
- announces
- 0
- likes
- 0