From: James Herdman Date: 2009-08-12T22:04:46+09:00 Subject: Re: multiple projects - Apache --0016364edad4700bf20470f17641 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hi friends. The way I'm doing this is to have a single directory I symlink all of my app's 'public' directory to. I set this as my DocumentRoot and then have a single VHOST file for all of my apps. It isn't pretty, but it's fairly easy to parse with Ruby. So, my VHOST file looks something like this: DocumentRoot /u/apps RailsBaseUri /foo RailsBaseUri /bar # etc... I have had *zero* luck using multiple VHOST files. This may be due to my own lack of knowledge in using Apache though. You may wish to redirect your query to the Passenger mailing list though. They'll likely be of more help. Keep me posted though. I'd love to hear what your resolution is. James H. On Wed, Aug 12, 2009 at 8:28 AM, Jason Stewart wrote: > Excerpts from Joe's message of Tue Aug 11 14:31:53 -0400 2009: > > Hi, > > I'm trying to configure Apache so I can create multiple rails projects > without > > modifying httpd.conf everytime. Right now, I have one project setup and a > > apache virtualhost that points to it. Here is how I have it configured. > > > > > > ServerName rails.example.com > > DocumentRoot /var/www/rails_project/public > > RailsEnv development > > > > Hi Joe, > > AFAIK, that's not possible with passenger. I believe that a new vhost is > needed for every rails application on your machine (someone please > correct me if I'm wrong). > > If you have an existing vhost with something else on it, you can specify > that your rails application is in a subdirectory of that document root > like this: > > > ServerName rails.example.com > DocumentRoot /var/www/rails_project/public > RailsEnv development > RailsBaseURI /rails > > > Regards, > Jason > > --0016364edad4700bf20470f17641--