managing multiple rails applications with apache

how can manage multiple rails applications with apache

i have followed the following tutorial and successfullt set up my
rails site using apache

http://www.howtoforge.com/ruby_on_rails_debian_etch
http://www.howtoforge.com/ruby_on_rails_debian_etch_p2

but how can i configure apache to host more than one rails site ?

I wrote a little about this here:
http://skandragon.blogspot.com/2007/10/mongrel-apache-and-rails.html

How to set up Apache for multiple hosts (assuming no SSL) is pretty
easy, and well-documented in many, many places. Search for "apache
virtual host configuration" or similar. How to do it with SSL is even
easier, but burns one real IP address per host.

--Michael

Mongrel is a nice piece of software, but you should really have a look at Phusion Passenger. It effectively makes deployment of Rails applications as simple as deploying PHP code.

http://www.modrails.com/
http://www.modrails.com/documentation/Users%20guide.html#_installing_phusion_passenger
http://www.modrails.com/documentation/Users%20guide.html#_deploying_a_ruby_on_rails_application

It's on my to-do list. Right between rebuilding my Xen server, making
Asterisk work again, etc. :slight_smile:

--Michael

Thank you for your fast reply !

regards
Krishnan

Phusion Passenger is the easiest (and increasingly better) way:

http://blog.phusion.nl/2009/03/01/phusion-passenger-211-beta-released-thanks-sponsors/

Cheers, Sazima

+1 for Passenger. I'm currently running some Rails apps and a Sinatra
app as well on the same box. Very easy, very simple, very cool.

The only issue I have with Passenger is the same one I have for any
apache-module based application: Break into one, and you break into
them all.

That is, they all run as user www group www (on my box, those can
vary.) Therefore if applications cross administrative boundaries,
they must run on different Apache instances. Otherwise, one can read
another application's database.yml and the game is over.

That said, I'm the owner of my personal server, and therefore I am a
single boundry. I've started the conversion over to Passenger. One
down, 5 more to go. Looks trivial, and just works so far. The only
"site" I have it up on is my soon-to-be personal media database,
http://media.flame.org/ and no, it's not even close to done yet.

--Michael

Michael Graff wrote:


The only issue I have with Passenger is the same one I have for any
apache-module based application: Break into one, and you break into
them all.
That is, they all run as user www group www (on my box, those can
vary.) Therefore if applications cross administrative boundaries,
they must run on different Apache instances. Otherwise, one can read
another application's database.yml and the game is over.

Passenger solves that problem: