Hank, Thank you for your response.
I can deploy on a dedicated server so am not short of memory or cores but I am not expecting very high transactions volumes. So my preference would be to have a single (pack?) of mongrels handling the requests. Each domain would be handles by an Apache Virtual Host acting as a Mongrel proxy which would do a few things: 1) Set the document root. 2) redirect to maintenance pages if they are present 3) handle any cache hits 4) manipulate the headers if would like to (somewhere to put some other information if we want to pass data to the mongrel's). So effectively each of the Apache virtual servers will point to the same pack of mongrels defined in mongrel_cluster.yml which will point to the same rails app. #2 - I have designed the application so that it is really only one application so I would suspect I might be ok on this one, but certainly it would be a consideration for other applications. #3 - even if application.rb is shared, cannot I over-ride the :session path with the domain name in there to effecively partition the sessions by domain. I am not sure where I would actually over-ride this. environment.rb? application.rb? routes.rb (in particular The same goes for over-riding the page_cache_directory so the pages are cached to the document root of the apache virtual host. #4 - if there a way of testing if there is a domain specific version of a template or view and render that, if there isn't use the shared version. I am not sure I am looking at this part correctly. Thank you again for your help. Owain. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
