I looked into using Nginx earlier last year for reverse proxy and load balancing, and I have to say that I abandoned it due to the poor documentation - it was insanely hard to get any actual information on settings and configuration beyond sample rules.
I found the Lighttpd documentation quite good. It was certainly easier to set up (for me) than Apache. The simple vhosts mechanism is great; just create a new directory (or symlink) for each vhost. No need to edit the configuration files.
The problem is that nginx does not support IPv6 which is kind if sad for a "modern" HTTP server.
Not sure what universe in which you reside, but in this one nginx has supported IPv6 since 0.7.36, released in 21 Feb 2009. Sauce: http://nginx.net/CHANGES-0.7
I spent one whole year with Lighttpd - and never again will I go back. It "gets the job done", no doubts there, but in terms of managability and ease/versatility of configuration, it just cannot compare itself with Apache.
That's all well and good 'till one of your clients wants to use a.htaccess file.
I make some use Nginx for my own sites on my own dedicated servers (and it works great for that), but for my shared web hosting clients, I need to use Apache because all kinds of common software like CMS systems want to use.htaccess files, and Nginx doesn't support that.
If the Nginx project wants to take a good share of the shared hosting market, they are going to need to come up with support for.htaccess files, and the Apach
The difficult we do today; the impossible takes a little longer.
about time (Score:0)
Time to upgrade, this isn't 1995 anymore.
Re:about time (Score:3, Informative)
Right. Upgrade to a modern HTTP server like Nginx http://www.nginx.net/ [nginx.net] or Lighttpd, you won't regret it.
And if for some reason you really need Apache 1.3.x, this code is maintained by OpenBSD and an enhanced version is shipped with the OS.
Re: (Score:3, Interesting)
Re:about time (Score:5, Interesting)
Re: (Score:2)
Either it is a joke, or it was ages ago.
Nginx has a completely decent documentation: http://wiki.nginx.org/Main [nginx.org]
And some tutorials to begin with: http://nginx.org/en/docs/http/request_processing.html [nginx.org] - http://nginx.org/en/docs/http/server_names.html [nginx.org] - http://nginx.org/en/docs/http/configuring_https_servers.html [nginx.org]
Re: (Score:2)
Either it is a joke, or it was ages ago.
Or maybe he just didn't remember to think IN RUSSIAN.
Re: (Score:1, Informative)
The problem is that nginx does not support IPv6 which is kind if sad for a "modern" HTTP server.
Not sure what universe in which you reside, but in this one nginx has supported IPv6 since 0.7.36, released in 21 Feb 2009.
Sauce: http://nginx.net/CHANGES-0.7
Re: (Score:2)
I've been using it with IPv6 for months with no problems.
Re: (Score:1)
Re: (Score:1)
Re: (Score:2)
That's all well and good 'till one of your clients wants to use a .htaccess file.
I make some use Nginx for my own sites on my own dedicated servers (and it works great for that), but for my shared web hosting clients, I need to use Apache because all kinds of common software like CMS systems want to use .htaccess files, and Nginx doesn't support that.
If the Nginx project wants to take a good share of the shared hosting market, they are going to need to come up with support for .htaccess files, and the Apach