Date: Wed, 18 Jul 2012 07:48:44 -0400 From: Kevin Wilcox <kevin.wilcox@gmail.com> To: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> Cc: Paul Schmehl <pschmehl_lists@tx.rr.com>, FreeBSD Questions List <freebsd-questions@freebsd.org> Subject: Re: Apache vs. nginx Message-ID: <CAFpgnrM-S88mMkNn2z1DQKwNZQm0i%2BUMi4ntMqjKkGOTJz44zg@mail.gmail.com> In-Reply-To: <alpine.BSF.2.00.1207181118240.4799@wojtek.tensor.gdynia.pl> References: <35DA07557A36800645B39187@localhost> <alpine.BSF.2.00.1207181118240.4799@wojtek.tensor.gdynia.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 18, 2012 5:19 AM, "Wojciech Puchar" <wojtek@wojtek.tensor.gdynia.pl> wrote: >> >> I'm the admin for a small hobby website (Stovebolt.com - about 7 million hits/mo). We're fixin to buy a new server, and since I have to start from scratch (install FreeBSD and all the needed ports), I'm wondering if anyone on this list has switched from Apache to nginx. > > > it depends of your needs. This is a fantastic statement (I'm being serious, not facetious), because it really does. For specific purposes - serving static content with few bells and whistles, dedicated PHP application servers for custom apps and stuff like Drupal, I can't see ever going back to Apache. The nginx configs are too clean and too simple. For a large site with more complex authentication and access restriction needs that are handled by the web server, I wouldn't drift from Apache - not because I think nginx couldn't handle it but because I don't know if it could and because I am less comfortable with saying I did it properly with nginx than saying the same thing about Apache. kmw
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFpgnrM-S88mMkNn2z1DQKwNZQm0i%2BUMi4ntMqjKkGOTJz44zg>