Rails 2.3.2 + Lighttpd


#1

Can’t start empty Rails 2.3.2 project from Lighttpd:

2009-03-18 08:52:13: (mod_fastcgi.c.1047) the fastcgi-backend
/var/www/rails/public/dispatch.fcgi failed to start:

./script/server works fine.

Also Rails 2.2.2 works fine on Lighttpd.

Was there some changes in 2.3.2, do I need new configuration for 2.3.2?

$HTTP[“host”] =~ “^(mydomain.com)$” {
server.error-handler-404 = “/dispatch.fcgi”
server.indexfiles = ( “dispatch.fcgi”, “index.php”, “index.html”
)
fastcgi.server += (
“.fcgi” => (
“localhost” => (
“min-procs” => 1,
“max-procs” => 1,
“socket” => “/tmp/rails.socket”,
“bin-path” => "
/var/www/rails/public/dispatch.fcgi"
)
)
)
}


#2

I dont think many people use lighty and fastcgi these days, you may be
better off switching to NGINX/mongrel or passenger which most people
are doing??

I don’t know if lighty will continue being able to run newer versions
of rails forever as it seems to be a die-ing web server, sure you
could probably make it work, but I don’t know whether you would want
to.

I don’t particularly see why you would want to stay so current with
your rails version whilst using what is considered aging/under
performing deployment method…

Not criticizing just wondering?

Best of luck… I was bummed Lighttpd died too but I moved on.

Cheers

Richard
On Mar 18, 4:41 pm, Fresh M. removed_email_address@domain.invalid


#3

I don’t particularly see why you would want to stay so current with
your rails version whilst using what is considered aging/under
performing deployment method…

I need Rails 2.2 + Rails 2.3 + PHP + Perl support on web server.
And Lighttpd was simples way to make it all work together.
I can “ln-s phpmyadmin” to rails public and it works, also awstats
(perl) statistics works without any problems.