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.
Re:Restarting
jk2addict on 2007-08-07T13:17:43
Maybe RoR was the problem, not lighty.;-) Re:Restarting
ChrisDolan on 2007-08-08T00:25:31
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.Re:Restarting
sigzero on 2007-08-10T11:57:33
I feel sorry for Rails bashers. It is just too easy. They should pick something harder to bash.
Re:Troubleshooting?
jk2addict on 2007-08-07T15:58:02
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.
