I've always used Apache as webserver, just because that's what I'm used to.
It seems that Nginx is now (by far?) the most popular server. Is there any particular reason why it's become so popular? What's the main advantage over Apache?
@0PT41N Thanks, I'll have a look at that site!
Apache can also do reverse proxy. I have several services set up like that. But maybe Nginx had that functionality earlier?
> Is there any particular reason why [nginx has] become so popular? What's the main advantage over Apache?
My (potentially hot?) take is that you've stuck with Apache long enough that it's back to being a good option. There was a pretty good while when nginx was *dramatically* faster (esp. for static content) and easier to use modularly — but I believe Apache has now pretty much caught up. See https://www.jupiterbroadcasting.com/15401/nginx-vs-apache-techsnap-39/
(That said, I've always used nginx without any real complaints)
That could definitely make sense. I mainly use webservers for small-scale personal stuff where I'm mostly not that interested in performance.
(Ironically, that's probably the kind of projects where you could see the largest benefits. 😀)
@mogwai I found Apache very unstable on single board computers with not much RAM. I spent a lot of time trying to tweak webserver parameters so as not to run out of memory, but in the end Nginx worked far better.
My guess is that Apache was designed for large deployments on systems where there are few resource constraints.
@bob Probably, yes.
Apache feels like a big "monster" sometimes.
I haven't tried it on an SBC, yet. And hearing you, I probably won't try it. (Or at least I'll be very cautious.)
@mogwai Personally I use nginx to serve my personal siteS on my personal server!
I find it quite easy to configure, but I haven't compared the two.
@mogwai Apache's config format is weird and inconsistent. support for running applications in-process has caused Apache to be more complex, but nginx's proxy-only approach allows it to focus on doing just one thing well.
@mogwai it started with Ruby on rails. It was better to run on nginx. Then it stuck around and got better.
@mogwai not having to write XML config is very compelling.
Also I've never been able to get websocket proxying to work in apache but it's like 1 line in nginx and actually works.
@mogwai when looking for my first web server/reverse proxy, Nginx's configuration syntax was a lot less scary
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.