On Mit 20.09.2006 11:18, Paul Butcher wrote:
We have been searching for a Rails deployment architecture which works
for us for some time. We've recently moved from Apache 1.3 + FastCGI to
Apache 2.2 + mod_proxy_balancer + mongrel_cluster, and it's a
significant improvement. But it still exhibits
I have Mongrel 0.3.13.4 running Rails 1.1.6 behind Apache 2.2.3 with
mod_proxy_balancer, mongrel_cluster 0.2.0 as per the documentation,
and mongrel_upload_progress 0.2, on Fedora Core 4. I'm using a
cluster of three Mongrels.
I have an existing app which allows users to upload files, and
My question is about the static files in the Rails public folder. These
files should be served by Apache instead of Mongrel, so do I need to
upload these files to Apache's htdoc's or will Apache cache them the
first time they are requested from Mongrel... Im not sure how this works?
Many
Well, right now I use mongrel for deploying my live rails apps. Pretty
standard I guess. I've currently been using mongrel_cluster, but I
would like to eventually use some kind of process monitoring (monit?).
I have yet to really look into it though. The book really should cover
how to use mongrel
I'm working on the Mongrel book with Zed, and wanted to get some
feedback from the core users (this list) about how they use Mongrel.
That sounds a bit vague, but I'm interested in hearing things about
frustrating problems / workaround, preferred configurations, if you
have a particular way
Hi!
Take a look at this document: http://mongrel.rubyforge.org/docs/
apache.html
You should leave the static files in the public folder of your
application, and configure Apache to use rewriting (see section
Configuring Apache2).
Regards,
Hendrik
Am 21.09.2006 um 16:27 schrieb Kris
Hey,We use the following elements for our deployment:1. A hardware load balancer with two servers as backends, each running:2. One lighttpd instance, routed to a pound acting as a load balancer, each with:
3. Two mongrel instances.4. A monit process on each server monitoring pound, lighty
On 9/20/06, Matt Pelletier [EMAIL PROTECTED] wrote:
I'm working on the Mongrel book with Zed, and wanted to get some
feedback from the core users (this list) about how they use Mongrel.
That sounds a bit vague, but I'm interested in hearing things about
frustrating problems / workaround,
On 9/21/06, Kris Leech [EMAIL PROTECTED] wrote:
My question is about the static files in the Rails public folder. These
files should be served by Apache instead of Mongrel, so do I need to
upload these files to Apache's htdoc's or will Apache cache them the
first time they are requested from
Have you ever use haproxy http://haproxy.1wt.eu/ ?!
In a word, no :-)
He have the following feature which can help you:
Thanks - sounds interesting. We'll give it a go!
--
paul.butcher-msgCount++
Snetterton, Castle Combe, Cadwell Park...
Who says I have a one track mind?
MSN: [EMAIL
On Wed, 2006-09-20 at 19:22 -0700, Zed Shaw wrote:
On Wed, 2006-09-20 at 18:26 -0400, Ian C. Blenke wrote:
First off: Our clusters are LVS balanced Apache 2.2.3 +
mod_proxy_balancer + gem mongrel 0.3.13.3 / mongrel_cluster 0.2 +
memcached / gem memcache_client + gem rails 1.1.6 on debian
With Mongrel using Sync, are there any potential problems with actions
that start threads and use Mutex?
Steve
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
On Thu Sep 21, 2006 at 07:52:05AM -0700, Carl Lerche wrote:
You know, I'm going to add to this. I love mongrel. Simple, easy to
use, flexible, etc... You're doing an amazing job with it :)
mongrel is so easy to use, i dont even know im using it. actually removed all
traces of webrick from
13 matches
Mail list logo
