similar to: mongrel 1.1.3 breaks camping; use 1.1.2 instead

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:

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 all, I''m not sure who Camping''s steward is at this point(zimbatm? _why?), but I haven''t seen much activity in quite some time. I really like Camping, and I understand open source projects can fall by the wayside. So, I''d be willing to take over maintenance and releasing. I have experience maintaining my own open source projects, and a history of

Hey Everybody! I was wondering if/how Camping can process more than one request at once (i.e. not what Rails does). I''m fairly new to threads, and I bought a book, and read some of it, and dived into the Camping source... I found some thread stuff but I''m not... entirely sure. So I thought I would ask! RYan. http://yeahnah.org/

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

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

Why is the camping handler using Mutex#synchronize to serve requests? I was under the impression that camping was considered more thread safe than Rails? -Zach

I''ve been having some trouble with certain apps under Camping with Mongrel, particularly when lots of static files get served. So, I''ve borrowed some ideas from the RailsHandler and tightened up the Mongrel::Camping classes which come with Mongrel. If you''re having any troubles or want to test it out, update from Mongrel SVN and then `rake install`. It should produce

Hi, I and a few folks on #camping thought it would be nice to have either cookie based or file based session handling. This would eliminate the need for creating a sessions table in the database (or a sequence), which feels too heavy for a lightweight framework like Camping anyway. Plus, we can more easily avoid nasty adapter errors. :) The general consensus was to create a separate

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

{} || || ~~~~~~~~~~~~~~~ <= _whycake ~ Camping 2.1 ~ ~~~~~~~~~~~~~~~ I''m pleased to announce another release of Camping, the microframework. This time we''ve focused on improving the 1.9 support, adding (builtin) support for more template engines, refreshing the homepage and just general bug fixes. gem install camping Home:

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

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

Hello, Zimbatm suggested the best way to push a patch into camping was to take my case to the people. So here it is. If you want to jump straight to the patch: http://code.whytheluckystiff.net/camping/ticket/117 Goal: Move the logic in the camping command line launcher into several classes Why? In the next version of parasite (http://parasite.rubyforge.org) I''d like to take over

And now: gem install camping --source code.whytheluckystiff.net I hope this will be the last development release before 1.5. * ActiveRecord no longer required or installed. * If you refer to Models::Base, however, ActiveRecord will be loaded with autoload. (see lib/camping/db.rb) * new Camping::FastCGI.serve which will serve a whole directory of apps (see TheCampingServer[1]) *

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

I''m just about ready to release 1.4.2. Here''s the pre-release: gem install camping --source code.whytheluckystiff.net The biggest recent change is that the Camping commandline tool now allows mounting of several apps. I''ve eliminated examples/serve and am encouraging use of the camping tool. Instead, use: camping examples/blog/blog.rb examples/tepee/tepee.rb

Getting Camping to work with FastCGI is a little clunky, since FastCGI doesn''t really understand mounting apps and sometimes the environment vars are a little whack. To keep the postambles easy to read, I''ve moved the handy stuff into lib/camping/fastcgi.rb. == Mounting a Single App Assuming: Camping.goes :Blog ... this goes in your postamble ... require

Okay, let''s see. gem install camping --source code.whytheluckystiff.net A bunch of great stuff. * Camping::Apps stores constants for all loaded apps. * bin/camping can be given a directory. [1] Like: camping examples/ * Console mode -- thank zimbatm. Use: camping -C yourapp.rb * Call controllers with Camping.method_missing. Tepee.get(:Index) #=> (Response)