What’s the current suggested best way to host Rails behind Apache 1.3?
If the answer is Mongrel and mod_proxy, do the (common) directions
for Apache 2.2 hold for 1.3 as well?
-faisal
Coda Hale’s blog article at
http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you/
is a useful introduction to Apache/Mongrel. I’m not sure if it’s the
“current suggested” way to do it, but it has been lightning fast and
very flexible for me (with regards to single solution that handles both
static and rails content).
c.
Faisal N Jawdat wrote:
What’s the current suggested best way to host Rails behind Apache 1.3?
If the answer is Mongrel and mod_proxy, do the (common) directions
for Apache 2.2 hold for 1.3 as well?-faisal
On 9/15/06, Cayce B. [email protected] wrote:
Coda Hale’s blog article at
http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you/
is a useful introduction to Apache/Mongrel. I’m not sure if it’s the
“current suggested” way to do it, but it has been lightning fast and
very flexible for me (with regards to single solution that handles both
static and rails content).
That’s for apache2.2. For 1.3 you might use the multiplex option in
mod rewrite. Never tried it but in theory it should work.
Chris