For cruisecontrolrb.thoughtworks.com (which basically runs on
RubyWorks 1.1 RPMs with somewhat modified configuration):

> * Framework, if any (Camping, Merb, Rails, Nitro, Ramaze, IOWA, Rack...)
Rails

> * Mongrel version
1.0.1

> * Mongrel handlers used
rails, dirhandler

> * How many mongrel routes and handlers per route registered
mongrel_rails defaults

> * Any Mongrel plugins used
none

> * Mongrel runners used
mongrel_rails, non-detached (i.e., no --daemon option), launched from runit

> * Number of mongrels per server per app
4. No reason other than it's a sensible default number (i.e., never
needed to optimize it).

> * Monitoring system
monit and runit
technically, runit is not a monitoring system

> * Proxy or software loadbalancer, if any (apache mod_proxy_balancer, nginx, 
> pen...)
HAProxy

> * Caching strategy
Rails page cache

> * Whether you serve media assets via mongrel itself, as opposed to through a 
> webserver.
Apache via mod_rewrite URL matching

> * Operating system including distribution or version
Linux (CentOS 5)

> * Architecture, via 'uname -a' preferably (x86, x86_64, Sparc, PPC, Arm (ha), 
> JRuby)
x86_64

> * CPU count
4 dual core CPUs on a VM host running several virtual machines.

> * Ruby version including custom distribution patches
1.8.6 p36, from RubyWorks RPM repo. Upgrade to p111 is planned soon-ish.

Lots of people are running 1.8.5 p35 with patches, as that is what
mainstream Linux distros (RedHat, Debian, Ubuntu) provide.

> * Rubygems (yes/no, version)
yes, 0.9.4

> anything weird
Nothing that you don't already know about.

-- 
Alexey Verkhovsky
CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com]
RubyWorks [http://rubyworks.thoughtworks.com]
_______________________________________________
Mongrel-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/mongrel-users

Reply via email to