similar to: Instructions for virtual hosting with Apache + Mongrel?

Hi, I run a small web hosting company. We host a few Rails applications using Apache 2.2 and mod_fcgid. I have been experimenting with Mongrel and mod_proxy. But I can''t seem to figure out how to host multiple Rails - apps with mongrel. Do I have to start a new Mongrel process for every virtual host on a different port? Any help would be great. MJ -------------- next part --------------

Ok, a refinement of the question I asked yesterday (If there were any replies from yesterday I don''t have access to them here .. sorry if I''m duplicating anybody''s words here). How can one host multiple domains with mongrel? Assuming you are mass vhosting and you also want the performance benefits of using mongrel ... As far as I can tell, one could set up a

I have apache 1.3 with mod_ssl in front of mongrel/rails. Apache is setup to require client certification, and I''m trying to figure out how to pass the ssl env variables to mongrel. Here is the apache config to proxy requests to mongrel. I haven''t tried to pass env variables like this before so I''m not sure if it''s the apache config I have wrong, if mongrel

There is a big difference if you are not running a pure rails site. I am doing auth apache-side because I serve static content, perl scripts via cgi and feed the mongrel pack from Apache. The REMOTE_USER variable value can be passed to rails using a technique described deep down in one of the informative pieces on the Mongrel website. Bill On Mon, 12 Mar 2007 17:54:07 -0700, Matte Edens wrote:

Dear Mongrel users, I would like to use Mongrel to introduce RoR on an existing Apache/PHP server. The server serves several domains, set up as virtual hosts. The idea is to install a Rails application to be used in addition to the existing configuration. Example: www.domain1.com/index.php -> Via Apache www.domain1.com/appname/controller/action -> RoR application I am at a loss how to do

Cheers, I''ve just published a blog post about scaling Rails with Apache 2.2, mod_proxy_balancer and Mongrel. This way you do not need another proxy server or load balancer for Mongrel. Just use Apache 2.2 and mod_proxy balancer. http://blog.innerewut.de/articles/2006/04/21/scaling-rails-with-apache-2-2-mod_proxy_balancer-and-mongrel Jonathan -- Jonathan Weiss

Let''s try this one... I have Apache 2.0.55 set up and also have Mongrel set up. I have Radiant set up running under Mongrel, and have Apache proxying to the Mongrel instance. That all seems to be working fine. I thought I''d modify the settings a bit to let Apache serve up the static files - images, stylesheets, etc. I have it set up, and am not getting any errors. However.

Hi Folks, We''re moving from a single lighttpd-hosted Rails box to a Apache/ mongrel cluster. In lighttpd, mod_compress had a very nice feature: if there''s a static file, it would compress it in a user-specified compress folder. If the file hasn''t changed, it would just serve out the compress file; if the file has changed, it would recompress it and serve it out.

Our Mephisto install kills Mongrels and causes Apache to pound the CPU. This started when we moved to Apache+mod_proxy_balancer+Mongrel. Here''s what we know: The following things are working OK, except when used in the combination listed above: mongrel, mongrel_rails, MySQL, Apache, mod_proxy_balancer. We believe these are all OK because we moved five other Rails apps to this

Hello, I want to install a bunch mongrel servers with an apache in fronthead, all that on OpenBSD. But OpenBSD is released with a homemade Apache 1.3.29 patched by the OpenBSD team. I really want to keep this version of apache and I don''t want to change it to Apache 2.x (because of the security and the license but it''s not the point here). But for having mongrel, it has to be

Hi, There''s lots of stuff going on currently with choices of production deployment environments. But I''m not clear on a few things as I need to decide on a production setup where Apache is a given. A recent thread (http://www.ruby-forum.com/topic/56590) seemed to favor Apache 2 with mod_fcgid. And this is supported in articles such as:

Happy RailsDay! While everyone else was out having fun with RailsDay I spent my time wisely and wrote up tons of documentation for Mongrel and cleaned out some of the docs I''ll never write anyway. I also took the time to apply some nice patches from Jonas Pfenniger for easily setting up redirects in Mongrel. Some of the highlighted documents people will be interested in are: *

I''m trying to understand the ''Big Picture'' of how Ruby on Rails applications are deployed and operate in distributed environment (one deployment server, many remote servers). I follow AWD by Dave Thomas'' explanation from pages 624-626. From reading these pages I have these questions; 1. How does the RonR instance on the ''remote'' server gain

Howdy, I''m trying to debug a situation where a Rails app running on Mongrel +Apache stops listening to requests. Restarting Mongrel and Apache brings it back to life. First off, here''s some info on versions, etc...: Red Hat Enterprise Linux ES release 3 (Taroon Update 8) ruby 1.8.5 (2006-12-04 patchlevel 2) [x86_64-linux] Mongrel 1.0.1 Rails 1.2.1 fastthread (0.6.2)

I''m running Apache 2.0 as a proxy to several Mongrel/Rails apps, so that all of my Mongrel apps can be routed through the single Apache IP address. Apache 2.0 is already in use on the system, which is why I haven''t decided to use Apache 2.2. The problem I''m having is that this setup only works for Rails apps that do not use the public/index.html file as the main

Hi Folks, I''m sure tons of people are gonna ruin a whole drawer of their best panties over this one. Rick Olson worked on the mongrel_upload_progress gem, documentation and examples and has almost everything you need to do progress tracked file uploads using just Mongrel to handle the upload. This means that Rails (or any other framework) isn''t blocked while the upload

Hi, I have a setup with apache 2.2.6 proxying requests to a cluster of 5 mongrels. Occassionally, I receive the following error in the logs: [Tue Oct 30 12:00:28 2007] [error] (70007)The timeout specified has expired: proxy: pass request body failed to 127.0.0.1:8013 (127.0.0.1) from 213.205.247.171 () [Tue Oct 30 12:00:28 2007] [error] [client 213.205.247.171] Handler for proxy-server returned

We are running Apache and Mongrel on RHEL4 and have been experiencing some interesting behaivor. Sometimes when someone logs into our application (it uses the acts_as_authencticaed and acl_system2) the following happens. Instead of the browser rendering the html and displaying all the form elements corretly as you would expect, it simple spews back the output without attempting to render. So

Hello, I want to install a mongrel rails server with an apache in fronthead, all that on OpenBSD. But OpenBSD is released with a homemade Apache 1.3.29 patched by the OpenBSD team. I really want to keep this version of apache and I don''t want to change it to Apache 2.x (because of the security and the license but it''s not the point here). But for having mongrel, it has to be with

Hi, I''ve got to active project both running on the last Apache 2.2 and on Mongrel 0.3.13.3. One is running perfectly, the other gets (always on the same pages, but not after each request, it seems to be random) a ProxyError every now and then which leads to the mongrel process being called to die and subsequently slowing down the whole web site. I have to restart the mongrel