similar to: logger & debug level

Dear Mongrels, The same questions keep coming up over and over on the list, which is ok, but not really optimal. If we added a wiki to the Mongrel site to handle FAQs, what wiki should it be? Required features would be: * Spam protection * Doesn''t look shitty I would probably spring for Trac (and also migrate the bugtracker) if noone else has opinions, but I''m sure some of

Hi Zed, I checked in a pure-Ruby URI classifier to Mongrel trunk. Ola''s Java port of the TST had some bug, and I don''t think it''s necessary in the first place. The Ruby classifier is around 25 lines instead of the 400-odd lines for the C extension and the 200-odd for the Java extension. It uses a Regexp which is perhaps shady: @matcher = Regexp.new(routes.map do

Hi all, 1.0.2 final will drop as soon as I get the win32 builds from Luis. Watch for it. In the future we won''t do RCs but will just make point releases, because no one really installed them except for ourselves. This is what Zed used to do and what we should have done all along. Note that the bug tracker is empty:

Hi all, Forgive me if this has been asked before, but is there a reason mongrel_rails cluster::restart stops all ports and then restarts them again? Wouldn''t it be better to restart each port one-by-one in series so that upstream proxy servers can fail over while the restart is occurring, or am I missing something? Thanks, eden

Which web server does mongrel fair best with? -Ron

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...) * Mongrel version * Mongrel handlers used (rails, dirhandler, camping,

Hello Everyone, Been head down with personal stuff, but I wanted to shoot out this email saying that I''ve collected the list of volunteers and decided that I''d just hand the keys over to them and see how they do. The list of people I have so far is: Ezra Zygmuntowicz <ezmobius at gmail.com> "Kirk Haines" <wyhaines at gmail.com> "Wayne E. Seguin"

I''ve been trying to track down the culprit of erratic behaviour and crashes on my production server (which is split into a number of Xen instances), so set up a staging server so that I could really try to get to the bottom of it. The staging server (also split with Xen) is set up pretty much identically as far as the mongrel_cluster server is concerned (the production box has two

i was searching the mongrel site and also this list, but didnt find any answer. maybe somebody can describe to me, what the differences are from mongrel 1.0 to 1.1 and which i should use in a production environment. regards, mz -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20071229/f3948be3/attachment.html

Hello, I''m running a Rails application which must sort and manipulate a lot of data which are loaded in memory. The Rails app runs on 2 mongrel processes. When I first load the app, both are 32Mb in memory. After some days, both are between 200Mb and 300Mb. My question is : is there some kind of garbage collector in Mongrel? I never see the two Mongrel processes memory footprint

A new TRAC entry with patch has been added (initially for Camping) to allow X-SendFile on Windows to use DirHandler to send files on drives other than the current drive, if the DirHandler base path is "/" (which is the way Camping uses DirHandler). As it was, "/" gets expanded to "C:/", and then you can''t serve files on any other drive, which I needed to do

Hey so, People are asking about Mongrel Ruby 1.9 compatibility. Isn''t the point of 1.9 for library developers to have time to get ready for 2.0? It''s not like 1.9 is a production release. Evan -- Evan Weaver Cloudburst, LLC

Hi all, Is there any integration with testing tools such as RSpec or Test::Unit planned? I see that the cruise task is run correctly, but the tests show up underneath the build log. Ideally I''d like them to show up the same way that they do in ''java'' CruiseControl, in their own section of tests. Will.

Is the dashboard output of 1.2.1 supposed to validate (I get numerous failures)? I''m seeing some issues that I hadn''t been running into before my upgrade. The first time I load the dashboard I''m seeing a blank area at the top and first button isn''t styled. When the refresh triggers the all of the projects except the first are duplicated and the

As of now, I can create a project from Git repository, run a builder on it, and even run the dashboard. Build pages look ugly because build.label in git is very long, a bunch of unit tests is failing, and I had to disable some functionality, namely displaying source control errors in the dashboard. SourceControl::AbstractAdapter#execute_with_error_log (formerly known as

Hi, I''ve done some benchmarking on our new servers (being built now), AMD X2 5600, gentoo-hardened. With the same CFLAGS (safe cflags: -march=k8 -O2) I''ve tested the following configs: 1, emerge ruby rubygems, then gem install mongrel (or emerge mongrel, the performance was similar) 2, download the same ruby version, untar, ./configure, make, make install, download rubygems,

Hi Friends, Just happened to catch this err in the CC log: Build loop failed BuilderError: Write failed: Broken pipe ./script/../config/../app/models/subversion.rb:98:in `execute_in_local_copy'' ./script/../config/../lib/command_line.rb:86:in `call'' ./script/../config/../lib/command_line.rb:86:in `e'' ./script/../config/../lib/command_line.rb:84:in `popen''

Hello all. I too found out that I sometimes have some action that can take up to 10 seconds in my rails application. I''ve read all arguments Zed made about polling/and inbox strategies, and I think I just can''t work around my feeling that a "wrong" request that takes up too much time should be able to lock subsequent requests in mongrels queue. That''s what

Hello Guys, I''ll like to suggest a small release fix before we start doing big changes: platform fixes. Current we''re setting MSWIN32 (mswin32) as platform for Windows gem, but we should be using Gem::Platform::CURRENT instead (i386-mswin32 as current Ruby windows implementation). Also, the jruby/java platform need to be defined. That change will ease the compatibility path

The build has been fixed. CHANGES ------- Revision 8820 committed by bitsweat on 2008-02-07 23:10:01 Remove empty .rhtml templates D /trunk/actionmailer/test/fixtures/templates/signed_up.rhtml D /trunk/actionmailer/test/fixtures/helper_mailer/use_example_helper.rhtml D /trunk/actionmailer/test/fixtures/first_mailer/share.rhtml D