similar to: mongrel_service build

Hi all, Release candidates for *nix 1.0.2 and dependencies are up at http://mongrel.rubyforge.org/releases/ . Public cert is at http://rubyforge.org/frs/download.php/25325/mongrel-public_cert.pem . Install with: sudo gem install mongrel -P HighSecurity --source=http://mongrel.rubyforge.org/releases/ etc. Luis is working on win32 builds. Evan -- Evan Weaver Cloudburst, LLC

Hi list, I downloaded and tried to install Mongrel (latest stable version) from the -win32 gem. Platform is Win2K. It said it needed daemons so got and installed that. Then it said it needed cgi_multipart_eol_fix (I think that was the name, not at my machine now, can confirm later and repost if needed). Googled for that but couldn''t find it. (Don''t have net connectivitity for a

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, There is a bug with Mongrel on JRuby 1.0.3 that the JRuby guys want fixed before they release it. If it''s ok with people I''d like to fix that, revert (at least for now) the proxy response change, and tag that as 1.1.2 and release it. Anything wrong with this plan? Evan -- Evan Weaver Cloudburst, LLC

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 Users!, Since the pre-release 0.3.18 (last week) Lot of things happen in ruby-land (check the DoS security bulletin, please). Anyway, the win32 folks being left on the side of the road, and cannot provide feedback of stability due lack of binaries for the latest releases. So, I managed to upload the pre-built gem to my host: http://www.mmediasys.com/releases/mongrel-0.3.18-mswin32.gem

I just ran into an issue with a new mongrel install on Win32. When trying to run mongrel from RadRails 0.7.2 on win32, I got an error while loading that it couldn''t locate mongrel_service. C:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require'': no such file to load -- C:/ruby/lib/ruby/gems/1.8/gems/mongrel_service-0.3.1/lib/mongrel_service/init.rb

Hello Mongrels, Release candidates for Mongrel 1.0.2 and its dependencies are now available. Note that gems are now signed, so please add the Mongrel public certificate via: $ wget http://rubyforge.org/frs/download.php/25325/mongrel-public_cert.pem $ gem cert --add mongrel-public_cert.pem Now you can verify and install the candidates via gem install: $ sudo gem install mongrel

FYI. -- - Brian Gupta http://opensolaris.org/os/project/nycosug/

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:

i was suffering from a massive memory leak in my application. after searching and testing for quite a while i finally found that it wasn''t my app that had a leak but the win32ole support that was used by the ADO driver in sqlserver adapter. the solution to fix the leak was to install ruby 1.8.5p52 or 1.8.6p36 but sadly as soon i install one of the fixed releases mongrel won''t

Konnichiwa Mongrel users, mongrel_service cannot run as a windows service under my environment, with the windows message : "error 1053 : The service did not respond to the start or control request in a timely fashion." >From a part of "ServiceFB.log" at c:/ruby/bin, mongrel_service failed to get the process name of "service.exe".

Hey Campers, Ditch that pup-tent for Camping deployment. Maybe. Either way, drive around in Rv 3, newly released *right at this moment*. Rv A little init.d system for running Camping apps, for Linux. Features * cluster support * custom database configuration * interactive setup tasks * logging Full documentation and instructions at:

Hey, I just finished a round of testing my app with mongrel-1.0rc1 (pretty good, four segfaults and a gc error in maybe ten thousands requests) and was moving on to mongrel_service to see if it could cope with said segfaults and gc errors. Sadly, the service will not start. I installed using: mongrel_rails service::install -N nplrails -e development -p 3000 claims to be happy. When I try to

Hi, why are the gemplugins commented out in mongrel_service? What was the problem with them? I''m curiuos because I''ve used them without problems since the revision 338 (-win32 suffix patch, 31/08). However, my site is a small internal one, so it doesn''t mean any heavy testing. Jano

Hello Esteemed Tent-pitchers, Can we get a point release of the current camping trunk? 1.5.1 maybe? I don''t know how stable trunk is, but there are lots of bugs that would be nice to get resolved. Particularly the ones involving the incorrect creation of the sessions table. Evan -- Evan Weaver Cloudburst, LLC

Hello! Run problems after upgrading to mongrel 1.0.3 from 1.0.1: # uname -sr FreeBSD 7.0-BETA1 # mongrel_rails start ** Starting Mongrel listening at :3000 ** Starting Rails with development environment... ** Rails loaded. ** Loading any Rails specific GemPlugins ** Signals ready. TERM => stop. USR2 => restart. INT => stop (no restart). ** Rails signals registered. HUP => reload

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

I''ve got my application running under Windows with mongrel perfectly, so it was time to convert it to a service. service::install works fine, but service:start gives me some "One moment, start pending" and then lots of "One moment, stopped". After a bit of digging I found this in the service.log: ** Starting Mongrel in production mode at :3000 ** Starting Rails in