On Jan 3, 2008 3:45 PM, Evan Weaver <[EMAIL PROTECTED]> wrote:
> Hello Mongrels,
>
> Building on the last messages about Fastthread, can we get a detailed
> survey of the different ways people are deploying their applications?
> It will help with near-future Mongrel development.
>
> Please include the following things:
>
> * Framework, if any (Camping, Merb, Rails, Nitro, Ramaze, IOWA, Rack...)

Rails, Merb, Small little MVC proof of concept :-)

> * Mongrel version

1.0.2 mostly.

> * Mongrel handlers used (rails, dirhandler, camping, cgiwrapper...)

Rails, DirHandler and custom made.

> * How many mongrel routes and handlers per route registered (if you
> don't know, it's probably <= 2)

<= 2

> * Any Mongrel plugins used (mongrel_upload_progress, mongrel_gzip,
> mongrel_cow_cluster, mongrel_experimental...)

none

> * Mongrel runners used (mongrel_rails, mongrel::cluster,
> mongrel_service, RV, others... please be *very specific* about which
> options of the runner you use. For example, some people use
> mongrel::cluster but only for the --clean functionality, not for the
> clustering).

mongrel_rails (development) mongrel_service (deployment)

> * Number of mongrels per server per app

3

> * Monitoring system (runit, monit, god...)

Custom made

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

Custom made TCP balancer, no proxy.

> * HW loadbalancer, if any (Netscaler...)

None

> * Caching strategy (memcached fragments, memcached object, squid,
> rails page cache, rails page fragments, ESI)

No caching

> * Whether you serve media assets via mongrel itself, as opposed to
> through a webserver

Via Mongrel

> * Operating system including distribution or version (OS X 10.4.10,
> Ubuntu/Linux 7.10, WinXP SP2, OpenBSD 4.1...)

Windows XP SP2 Professional
Windows 2003 Server
Windows XP SP2 Professional x64 Edition

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

x86 and x86_64

> * CPU count

1, 2 and 4 cores, single CPU
2 cores in dual-cpu installations

> * Ruby version including custom distribution patches,
> (1.8.6p110+threadhooks, 1.8.5, JRuby 1.1b1, Rubinius trunk... also
> note where you got it, in case it isn't clear, for example, OS X 10.5
> built-in, Ubuntu apt, Instant Rails, direct compile from source)
> * Rubygems (yes/no, version)
>

1.8.5-p114, i386-mswin32 build (VC6)
1.8.6-p111, i386-mingw32 build (GCC)

Both version build from scratch.

> Please mention anything else about your system that's kind of weird,
> and anything that's been particularly troublesome regarding mongrel
> deployment.

Well, it's Windows, what more weird than that could be added? ;-)

But seriously, no IIS on these installations.

All the deployment process is being distributed by Windows Installer
packages and rubygems. The distribution or deployment of updates for
the application is done through rubygems.

-- 
Luis Lavena
Multimedia systems
-
A common mistake that people make when trying to design
something completely foolproof is to underestimate
the ingenuity of complete fools.
Douglas Adams
_______________________________________________
Mongrel-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/mongrel-users

Reply via email to