Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

jk2addict (4946)

jk2addict
  (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

Journal of jk2addict (4946)

Monday August 06, 2007
11:15 AM

Apache is dead.

[ #34012 ]

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.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • (disclaimer #1: I'm a developer, not a sysadmin; disclaimer #2 this is anecdote not data [perl.org])

    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.
    • Maybe RoR was the problem, not lighty. ;-)
      • Haha. Rails bashing is oh so funny.

        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.
        • I feel sorry for Rails bashers. It is just too easy. They should pick something harder to bash.
  • So you didn't take the time to troubleshoot it properly and don't like editing config files. So therefore Apache must be dead and no one should use it? Huh?
    • Chill. I'm sure I could've wasted all night looking for the problem. But why? I don't really need Apache. I'd surmise most people don't. My mod_perl/xml/xslt/AxKit days have long since past.