Rails - Jul 2006 - Lighttpd for rails app subdomain apache for the rest

I want to host a rails app at mydomain.com/railsapp.  For technical 
reasons I have to leave mydomain.com on apache.  This means that I need 
to tell apache to proxy only requests for mydomain.com/railsapp to 
lighttpd.  I have deployed in a situation like this before around a year 
and a half ago but it was a real pain.  Lighttpd and rails have matured 
a lot in the year and a half since I did that ugly deploy so I was 
wondering if it has gotten any easier?

Example lighttpd.conf files, rails code samples, and general advice for 
getting this to work would be great.  The domain I am deploying to is 
already hosted at TextDrive so I will be deploying there and using 
webmin to configure apache and shell access to get to lighttpd.conf.


Thank you,
Matthew Margolis
blog.mattmargolis.net

> I want to host a rails app at mydomain.com/railsapp.  For technical reasons
I
> have to leave mydomain.com on apache.  This means that I need to tell
apache
> to proxy only requests for mydomain.com/railsapp to lighttpd.  I have 
> deployed in a situation like this before around a year and a half ago but
it
> was a real pain.  Lighttpd and rails have matured a lot in the year and a 
> half since I did that ugly deploy so I was wondering if it has gotten any 
> easier?
>
> Example lighttpd.conf files, rails code samples, and general advice for 
> getting this to work would be great.  The domain I am deploying to is
already
> hosted at TextDrive so I will be deploying there and using webmin to 
> configure apache and shell access to get to lighttpd.conf.
If you''re using apache 2.2.2 why not proxy directly from apache to
mongrel
and skip lightttpd/fastcgi all together?

You can tell apache to only proxy a certain location and I believe the 
latest beta (soon to be release) of mongrel supports "sub-directory"
rails
apps...

-p