search for: cloudbur

...ke the savings were in the static typing more than the TST. Do you know anyone who''s running a shitload of Mongrel routes in a single server? Is there any reason not to keep this change? I know that TST dude put some patch in his library just for Mongrel, but still. Evan -- Evan Weaver Cloudburst, LLC

...at 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 you do. What do you think? Evan, and the Mongrel Team -- Evan Weaver Cloudburst, LLC

...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

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

...rring unforeseen difficulties. Thanks, Evan, and the Mongrel Team PS. If you really don''t care about authenticity, and don''t want to install the public certificate, you can omit the ''-P HighSecurity'' option in ''gem install''. -- Evan Weaver Cloudburst, LLC

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

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

I''m confused. Wasn''t threading fixed in 1.8.6, negating the need for fastthread? Why is fastthread still a requirement of Mongrel? Just curious. :)

I just found a vulnerability in one of my web apps that was running Mongrel 1.1.2 where I could go to URIs like /.%252e/.%252e/.%252e/.%252e/.%252e/.%252e/.%252e/etc/passwd and it would serve the actual /etc/passwd file. The issue seems to be in lib/mongrel/handlers.rb in the change from 1.0.3 to 1.0.4 req_path = HttpRequest.unescape(path_info) - if @path - req_path =

...e.org/tracker/?atid=5145&group_id=1306&func=browse . JRuby support will come in 1.1 which could happen any day. I''m waiting on them to fix their own socket bugs; there''s nothing wrong with Mongrel. 1.0.2 is actually 1.1 with some reverts. Take care Evan -- Evan Weaver Cloudburst, LLC

I seem to have a (recent) problem with mongrel on NetBSD. I''m running a development release of NetBSD (called NetBSD-current 4.99.34). When I start mongrel, it listens on the IPv6 wildcard address, but not on the IPv4 wildcard: => Booting Mongrel (use ''script/server webrick'' to force WEBrick) => Rails application starting on http://0.0.0.0:3000 => Call with

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

Hi, my mongrel has crashed with following errors in the logfile: ** 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 (without restart). It might not work well. ** Mongrel 1.1.3 available at 0.0.0.0:3000 **

Howdy -- I''ve been tracking down mem leaks (oh, the fun...), and I think there is a clue in objects.log. There are a few mentions of this file, but usually Zed saying "look at this file and it will help you". Can anyone clue me in to what the actual columns mean? 18,Float,143952,256821,112869,,, 18,String,39543,41693,2150,24.727076,55.526376,2308.000000

I have been getting this error on the production server after rails was updated to 2.0.2 and moreover this worked perfectly in the development mode. This crash occurs when no one is using the app for an hour or so. This is the error that I get in the logs. (nohup.out file). The production log doesnt show anything unusual. Please help me out guys.

...ur system that''s kind of weird, and anything that''s been particularly troublesome regarding mongrel deployment. Evan PS. You can get some of the Ruby information via the ''tattle'' gem: $ gem install tattle --ignore-dependencies $ tattle report -- Evan Weaver Cloudburst, LLC

...s 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: http://blog.evanweaver.com/files/doc/fauna/rv/ Evan -- Evan Weaver Cloudburst, LLC

...ack to me? We''re putting together release candidates. I messed with your Rakefile; in order to sign the gem you''ll have to make yourself a gem certificate and send it to me and I''ll auth it against the official mongrel certificate and send it back. Evan -- Evan Weaver Cloudburst, LLC

...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

...eemed 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