On Fri, Jul 10, 2009 at 06:35:57AM -0500, Mike McGrath wrote:
Stuff like this comes up from time to time and the question I always
have
is: What is it we're wanting to do that we can't currently do with the
setup we have now? We're a group with a lot of turnover and almost
everyone knows how to use apache so why is it worth it to us to switch to
nginx?
If we are wanting "to serve static files faster", then yes, Nginx would
do that for us[0]. I use Nginx for all of my personal application
deployments, and I've been extremely impressed with it's speed and ease
of configuration. However, it's WSGI support is a bit questionable, so
we would only want to use it as for serving static files & reverse
proxying. You can also configure it to hit memcached before apache,
which is pretty neat.
Mike is right though, if it's not solving an real problems for us, we're
better off using what we are already familiar with until we see an
obviously need for it.
luke
[0]:
http://blog.webfaction.com/a-little-holiday-present