# Rails 2.3.2 + Lighttpd

**URL:** <https://www.ruby-forum.com/t/rails-2-3-2-lighttpd/163203>\
**Category:** Rails\
**Created:** [March 18, 2009, 8:41am UTC](https://www.ruby-forum.com/t/rails-2-3-2-lighttpd/163203 "2009-03-18T08:41:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![giga](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/b9bd4f/32.png) [@giga](https://www.ruby-forum.com/u/giga)\
**Post date:** [March 18, 2009, 8:41am UTC](https://www.ruby-forum.com/t/rails-2-3-2-lighttpd/163203/1 "2009-03-18T08:41:16Z")

</div>

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](http://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"  
)  
)  
)  
}

---

<div class="post-metadata">

**Author:** ![giga](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/b9bd4f/32.png) [@giga](https://www.ruby-forum.com/u/giga)\
**Post date:** [March 19, 2009, 6:28am UTC](https://www.ruby-forum.com/t/rails-2-3-2-lighttpd/163203/2 "2009-03-19T06:28:27Z")

</div>

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](mailto:removed_email_address@domain.invalid)

---

<div class="post-metadata">

**Author:** ![giga](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/b9bd4f/32.png) [@giga](https://www.ruby-forum.com/u/giga)\
**Post date:** [March 22, 2009, 4:32pm UTC](https://www.ruby-forum.com/t/rails-2-3-2-lighttpd/163203/3 "2009-03-22T16:32:32Z")

</div>

> 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.