All the Perl that's Practical to Extract and Report
use Perl Log In
jk2addict (4946)
(email not shown publicly)
http://today.icantfocus.com/blog/
AOL IM: chrislaco (Add Buddy, Send Message)
Yahoo! ID: chrislaco@sbcglobal.net (Add User, Send Message)
Jabber: laco@scribblewerks.com
Apache is dead.
Dead to me I say. Dead. Why do people use Apache any more, other than because "X doesn't run on lighttpd"?
In a week of tinkering rather than working on crap I should be working on, I decided to upgrade to MovableType4. I run 3.x as pure CGI. It's slow, but 4 was horrible slow as a cgi. So, I did the next logical thing, run it under FastCGI.
I already had it installed and working under Apache. For whatever reason, things didn't get much better and I was sicking of playing config games. So I installed Lighhttpd just for giggles.
I'm mostly done converting everything over to use it, and running MT4 under FCGI. Now the only thing running on Apache is Subversion access, and even then, I can just mod.proxy it through lighttpd.
So, why do people use Apache again? It seems like a brick doorstop if you're really not doing something like deep n dirty mod_perl or some such stuff.
Always late to the party.
an endless discussion thread about what features to include.
-- Jarkko Hietaniemi
Restarting (Score:1)
I've never experienced an Apache crash - ever. I helped admin a RoR/FastCGI app running under lighttpd on an Xserves and had to restart lighttpd at least weekly due to crashes. Thank goodness that RoR app was for internal use only.
Re: (Score:1)
Re: (Score:1)
When my Catalyst app crashes, it never brings apache down with it in my experience. If RoR can take down lighttpd over a FastCGI connection, then that's even worse news than lighty taking itself down.
The webserver should be agnostic to the technology at the other end of its FastCGI pipe.
Re: (Score:1)
Troubleshooting? (Score:2)
Re: (Score:1)