similar to: [mongrel_cluster] hosting multiple web sites via

I''m newbie to mongrel, I''m not able to config mongrel_cluster in order to host multiple web sites added/remove as apache VirtualHost. I followed codahale http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you/ mixed with Wiki Radiant (I use Radiant as a rails apps to be deployed, 1 domain 1 radiant sites with its own document tree

I''d like to use Mongrel_cluster with SSL on a green-field application (it can be configured however is best - initially, "ease of setup" is important, but then soon after will be scaling and response time). I''ve read a lot of emails on this topic, and checked out the Mongrel pages, etc, but I''m left with this question of what is recommended: For a

Is there anything mongrel cluster gives you that monit doesn''t? I''ll be using monit to monitor a number of other services anyways, so it seems logical to just use it for everything including mongrel. Chris

Hi mongrel users! I just posted a bad-ass capistrano file that automates *everything* for setting up an apache2+mod_proxy_balancer and mongrel+mongrel_cluster -- including apache2 setups. It''s based off Coda Hale''s guide and all Bradley''s work at fluxura and RailsMachine (thanks Coda and Bradley!). It''s, well, bad-ass, if I must say so myself. My favorite

I am using mongrel_cluster with mod_proxy_balancer and would like to enable compression (assuming it improves throughtput) and limit file size upload. I configured mod_deflate and LimitRequestSize in Apache, but in my trials looks like the proxied calls bypass those directives (the conf goes below). Is there a way to get this? -- fxn # Adapt this .example locally, as usual. # # To be

Good morning everyone, I am running apache 2.2.3 compiled from source and proxy load balancer as described on the mongrel site. I have a total of three sites, this setup works really well for two of them but for one of them, I keep getting "Forbidden" errors and this error in the apache logs: [warn] proxy: No protocol handler was valid for the URL /. If you are using a DSO version of

If this was in the docs, I''ve missed it. How can I have multiple mongrel clusters on a server? All the documentation that I am seeing seems to assume that I am only running one cluster.

Our group has several web apps developed in ColdFusion, PHP, and Rails. The ColdFusion and PHP apps are on an older server, and the Rails apps on a new server. Ideally, we''d like them all to share the same server. Our current setup for the Rails server is Apache2.2 with mod_proxy_balancer and mongrel_cluster. We''d like to have specific directories be processed and served by

I''ve posted this to rails-deployment as well. I have to administer a medium size rails app (1''5 million requests each day), recently I''ve switched from lighttpd + fcgi to apache + mongrel. In the following lines I am going to describe the platform: All machines are running Debian Etch, with 4 gb ram and dual core intel32 processors. Web server runs debian''s

I?m knew to rewrites on apache in combination with mongrelcluster. It?s urgend for me, because the server has an loadaverage about 10 :-((((( Ok so I?m using 3 mongrel-server on an mongrelcluster. The Loadbalancer ist apache I think, that my rewrites are not correct. Please can anybody check my rewrites ? That?s in my /etc/apache2/conf.d/rails.proxy_cluster.conf <Proxy

A question about mongrel, apache and authentication. I''ve got a Rails site with I think a very typical setup: a mongrel cluster behind an Apache proxy. So Apache''s handling the static stuff and it hands off dynamic content to mongrel. I want to put the site temporarily behind Apache''s basic authentication. What I get when I do this is that is a password prompt which

hi all, i''m working on deploying my app w/ apache and a mongrel cluster. i''ve started by copying the instructions and code from the agile rails book and everything seems to be working fine but apache isn''t forwarding my requests to mongrel the way i expect it should. there''s nothing in the rewrite logs and nothing but 404 errors in the apache error logs.

hey all, I have an app working great with apache2 and mongrel_cluster. However, I''m trying to run another application and now when I go to app1.comit falls to app2.com and the opposite. That''s probably because I messed up somewhere with the cluster. this is the content of my conf.d/app1.proxy_cluster.conf: <Proxy balancer://mongrel_cluster> BalancerMember

Hello everyone, I did some initial tests and it seems that mongrel does not support byte-range requests. Is this correct? The reason I ask is that the iPhone requires byte-range requests to work in order to stream audio or video from a web server. Thanks in advance, alan

I am using Apache2.2 + mod_proxy_balancer + mongrel setup and my mongrel.conf file(for apache is like this) 2 3 <Proxy balancer://mongrel_cluster> 4 BalancerMember http://127.0.0.1:9000 5 BalancerMember http://127.0.0.1:9001 6 BalancerMember http://127.0.0.1:9002 7 </Proxy> 8 9 <VirtualHost *> 10 ServerAdmin rags at

I''m in the process of setting up a mongrel cluster at the moment, and I''m running into a bit of an issue. Even worse is that I''m not sure whether this is a mongrel thing, or an Apache thing. While I''m inclined to think that this might be a balancer thing, I decided there was a higher chance hearing back from mongrel-users than from apache-users, so I''d

I started the mongrel_cluster and tried to use the RewriteRule to forward the requests to proxy_balancer just as the http://mongrel.rubyforge.org/docs/apache.html said. When I visited my site from a remote computer, I always got the error messages "Forbidden, You don''t have permission to access / on this server." Finally, I added the "Allow from all" property (in the

Apologies, this may be off-topic. I''ve been wrestling with upload issues and Apache 2.2.2 / mod_proxy_balanacer / mongrel_cluster / Mongrel on Mac OS X Server 10.4.5. Typically the first upload would be fine but the next would make the mongrel instance remain running (ps state = "R") essentially locking up that instance. Apache would then eventually do: [Fri Jun 16 16:45:54

Hi all, I?m new to the list. I''ve working with mongrel for the last week and have some quetion about mongrel cluster: Is this (being executed from the application folder): # mongrel_rails start -d -p 3001 -e production # mongrel_rails start -d -p 3002 -e production # mongrel_rails start -d -p 3003 -e production the same as: # mongrel_rails cluster::configure -e production -p 3001 -N 3

Hi, I''ve configured a rails application on my VPS to run on two mongrels. When I run curl on localhost, the starting page comes up fine. That is, mongrel is serving the app perfectly. The problem arises when trying to access the app on my ip through apache. I get a 403 error. Just to test things out, I''ve set generous permissions on the entire rails directory structure