# Best practice question: which way to run rails on webserver?

**URL:** <https://www.ruby-forum.com/t/best-practice-question-which-way-to-run-rails-on-webserver/93149>\
**Category:** Rails\
**Created:** [April 28, 2007, 10:44am UTC](https://www.ruby-forum.com/t/best-practice-question-which-way-to-run-rails-on-webserver/93149 "2007-04-28T10:44:15Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![pgundlach](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/b9e5f3/32.png) [@pgundlach](https://www.ruby-forum.com/u/pgundlach)\
**Post date:** [April 28, 2007, 10:44am UTC](https://www.ruby-forum.com/t/best-practice-question-which-way-to-run-rails-on-webserver/93149/1 "2007-04-28T10:44:15Z")

</div>

Hi there,

I’ve been using rails for some time on my webserver. First I used  
lighttpd with fastcgi and now I am using scgi. Both with an apache 2 as  
a main server using (mod-?)proxy to forward requests to the  
lighttpd/scgi servers. Is scgi still uptodate? I found lighttpd/fastcgi  
a bit troublesome: if I remember correctly once in a while the fastcgi  
process would be dead, no response. So I had to restart lighty once in a  
month or so. Using scgi was more stable, but I am not sure if this is  
still the way to go.

What is the current ‘best practice’ for running multiple independent  
rails apps together with other non-rails applications on a server?  
apache2 is a ‘must have’, but can be used as a proxy. What about  
mongrel? Any others?

Patrick