2 ms·
nginx seems to be the "in" server with the Rails crowd. For some things lighttpd is easier to configure than Apache and if you're running a recent version ther
by bayareaguy 18y ago
nginx seems to be the "in" server with the Rails crowd.
For some things lighttpd is easier to configure than Apache and if you're running a recent version there are neat things you can do with it's lua support, e.g. http://blog.innerfence.com/2008/05/31/presto-move-content-to-s3-with-no-code-changes/ http://blog.innerfence.com/2008/05/31/presto-move-content-to...
Apache is probably better for people who want to worry about their app first and their infrastructure second. After your app is under control and you have time to worry about performance and configuration then you may want to look at the others.
Then there's also other servers like Squid and thttpd. If you don't know why you would want one of them then you're probably better off not thinking about them for now. To be honest I don't know what thttpd has going for it these days. A previous company I worked for standardized on it early on and then ended up adding so much to it they would have probably been better going with Apache.
Anyone here have any good reasons to go thttpd?