similar to: Rv 3 released, with cluster support

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

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

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

Campers -- In a few weeks there will be a bunch of people in Portland, OR, for a conference. A long time ago some campers mentioned that might be a good time for us to get together and hold a mini CampingConf for a few hours. Is anyone interested? Does anyone want to organize it? I''m thinking Wednesday night, May 16. We could possibly get a spot at FreeGeek (not likely since they are

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

I''d like to add taggability to a model in the site I''m working on, and I wanted to get an idea of what people are using. I keep seeing that acts_as_taggable is deprecated, so I tried the acts_as_taggable_on_steroids. I also tried be_taggable. In any case, I figured I''d see what people use. thanks. -corey -- http://www.coreyhaines.com The Internet''s Premiere

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:

Hello Campers I''m not sure this is the right list to ask but: I''m using the junebug wiki (which is written in camping) for my own personal wiki. I''d like it to behave as a proper daemon, so it will start up at boot, get stopped properly at shutdown, keep a pid file in /var/run etc. This requires a little messing with the wiki script junebug makes in the wiki

So, I''ve stumbled across bleak_house (http://blog.evanweaver.com/files/doc/fauna/bleak_house/files/README.html) - this looks like it may help me track down what is causing the Memory leak I''m seeing (be it me, Ubuntu, Debian, or Puppet). First step: I''m going to clone the repo, branch Second step: Learn Ruby - shouldn''t be too hard. Third step: Do exactly what

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, I am using mongrel for a long time... But just now I see a problem. I am running 3 instances using mongrel_cluster and nginx as a reverse proxy. When I start the cluster I have a memory usage of 20MB per instance... In the end of the day this usage is something about 230MB for each instance. It should be a memory leak? Thanks for the help. -- Fernando Lujan -------------- next part

Is ruby on rails supports aspell spell check ? Is there any links for spell check for rails application ? All links I gone through are discussing about php but not ruby on rails? Plzzzzzzzzzz give me reply .... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this

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

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 Mongrels, Mongrel 1.1 is out with fullblown JRuby support, some reorganization, and some bugfixes. Also, Mongrel_cluster has been updated to 1.0.4. Go subscribe to the all-new news feed, because we probably won''t announce to the list anymore: http://mongrel.rubyforge.org/rss.xml Thanks Evan, and the Mongrel Team -- Evan Weaver Cloudburst, LLC

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

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