Comments on: Goodbye, Apache; hello, lighttpd! http://www.thetlog.net/2007/07/12/goodbye-apache-hello-lighttpd/ Fri, 10 Feb 2012 07:55:04 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: mic http://www.thetlog.net/2007/07/12/goodbye-apache-hello-lighttpd/#comment-35273 mic Thu, 24 Apr 2008 09:02:16 +0000 http://www.thetlog.net/2007/07/12/goodbye-apache-hello-lighttpd/#comment-35273 Hello, may you share how you converted the wordpress .htaccess file? Thanks! mic Hello, may you share how you converted the wordpress .htaccess file?
Thanks!

mic

]]> By: Sérgio Carvalho http://www.thetlog.net/2007/07/12/goodbye-apache-hello-lighttpd/#comment-28268 Sérgio Carvalho Fri, 13 Jul 2007 14:06:57 +0000 http://www.thetlog.net/2007/07/12/goodbye-apache-hello-lighttpd/#comment-28268 Been down this path, and eventually returned to Apache. Apache modules are just too powerful not to miss them in lighty. My final setup, which I shall eventually describe in my blog, is a streamlined frontend apache, running the new event MPM, and a backend apache with the prefork MPM and all bells and wistles. Each blog.com server can handle a couple million pageviews per day, with peaks of 30 frontend processes and 5 backend processes. Under static content request loads, servers can easily serve ten times this load with no stress. Frontend processes average about 15Mb RSS usage. Bonus with this setup: mod_rewrite (the real voodoo one, not lighty's stripped version) and the fabulous mod_cache. Oh, and a clean separation between static content and dynamic content servers. Been down this path, and eventually returned to Apache. Apache modules are just too powerful not to miss them in lighty. My final setup, which I shall eventually describe in my blog, is a streamlined frontend apache, running the new event MPM, and a backend apache with the prefork MPM and all bells and wistles. Each blog.com server can handle a couple million pageviews per day, with peaks of 30 frontend processes and 5 backend processes. Under static content request loads, servers can easily serve ten times this load with no stress. Frontend processes average about 15Mb RSS usage.

Bonus with this setup: mod_rewrite (the real voodoo one, not lighty’s stripped version) and the fabulous mod_cache. Oh, and a clean separation between static content and dynamic content servers.

]]> By: Pedro Timóteo http://www.thetlog.net/2007/07/12/goodbye-apache-hello-lighttpd/#comment-28261 Pedro Timóteo Fri, 13 Jul 2007 11:24:07 +0000 http://www.thetlog.net/2007/07/12/goodbye-apache-hello-lighttpd/#comment-28261 Not that I know of. I've had success converting <code>.htaccess</code> files to directives in the lighttpd config file, but, of course, that won't work for apps that change their <i>own</i> <code>.htaccess</code> file... Not that I know of. I’ve had success converting .htaccess files to directives in the lighttpd config file, but, of course, that won’t work for apps that change their own .htaccess file…

]]> By: Alcides http://www.thetlog.net/2007/07/12/goodbye-apache-hello-lighttpd/#comment-28258 Alcides Fri, 13 Jul 2007 10:13:39 +0000 http://www.thetlog.net/2007/07/12/goodbye-apache-hello-lighttpd/#comment-28258 Is there any how to make lighttp read the htaccess? I've seen a module that does the same for IIS, just wondering... Without that, most of my apps wont run :/ Is there any how to make lighttp read the htaccess? I’ve seen a module that does the same for IIS, just wondering…

Without that, most of my apps wont run :/

]]>