similar to: + camping 1.4.120

Not too different from their corresponding last releases, but documentation has been filled in for both. To upgrade: gem install camping --source code.whytheluckystiff.net And, here is a complete changelog: == Camping 1.5 * Camping::Apps stores an array of classes for all loaded apps. * bin/camping can be given a directory. Like: <tt>camping examples/</tt> * Console mode -- thank

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

Camping apps are supposed to be little independent apps, often contained in a single file, which create the database tables and manage them without hassle. These days it''s common to see in a Camping app: module Tepee::Models def self.schema(&block) @@schema = block if block_given? @@schema end end Tepee::Models.schema do create_table :tepee_pages,

Just up: gem install camping --source code.whytheluckystiff.net The changes: * Both bin/camping and Camping::FastCGI.serve now act according to the Camping Server specification.[1] * Docs are complete. _why [1] https://code.whytheluckystiff.net/camping/wiki/TheCampingServer

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

UNSUBSCRIBE On Oct 5, 2007, at 1:27 PM, camping-list-request at rubyforge.org wrote: > Send Camping-list mailing list submissions to > camping-list at rubyforge.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://rubyforge.org/mailman/listinfo/camping-list > or, via email, send a message with subject or body ''help'' to >

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

Hey, campineros. And many good handshakes to zimbatm for getting some patches applied. So, yeah, I''d really like to get rid of any serious dependancies with this 1.6 release. Anything that''s not in stdlib has to go. Of course, camping-omnibus will still assume the whole ActiveRecord, Markaby, Mongrel setup that''s in the history books. Metaid can be removed and

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

Hal Fulton has been e-mailing me about putting together a simple blogging package for Camping. Perhaps start with the blog in the examples and add a few things. Does anyone here want to collaborate with him? Or do any of you have your own works to offer? He''s mentioned he wants something with its own template syntax, but I think he could hack that in. _why

Dear camping users, having been contacted by Julian Tarkhanov, I am willing to prepare the next camping release. _why has given me his friendly approval, with the reserve that camping.rb should be lower than 4k. He also told me that he wanted to remove the ActiveSupport and Markaby dependencies. I am writing here to get the users input so that I don''t do any mistake. So far, my plans

Okay, I have tested mounting several of my apps under Lighttpd and Apache, both running FastCGI. I''m going to explain the configuration, but first: update. gem install camping --source code.whytheluckstiff.net == Mounting Root for Lighttpd+FastCGI == server.port = 3045 server.bind = "192.168.0.103" server.modules = (

Hi !!! I''ve just seen this message on http://redhanded.hobix.com/inspect/theCampingServer.html I''d really like to see distributions offer a package which would allow simple setup of TheCampingServer, just as you see with PHP. If you''re interested in seeing this happen for the upcoming Camping 1.5 release, introduce yourself on the

On Sat, Jun 03, 2006 at 10:27:28PM -0400, Axis Sivitz wrote: > I removed the specified lines of code, as that only dealt with detection > of non-camping apps anyway, and tried to run it again. The server > started, but going to localhost:3301/ yields the following error: In order to use bin/camping these days, you must use Camping.goes. So make sure: * Before you do anything else --

Camping now comes with a sessioning class, checked in tonight. To get sessions working for your application: 1. require ''camping/session'' 2. include Camping::Session in your application''s toplevel module. 3. In your application''s create method, add a call to Camping::Models::Schema.create_schema 4. Throughout your application, use the @state

I''ve noticed that the copy of Mongrel installed by the camping-omnibus gem doesn''t work with Ruby 1.8.6. Or to be more specific, cgi_multipart_eof_fix (which Mongrel is dependent upon) doesn''t work: > $ sudo gem install mongrel --source http://code.whytheluckystiff.net > > ERROR: Error installing mongrel: > cgi_multipart_eof_fix requires Ruby version

hi all, curious about your input on this latest design experience i''ve had with camping. none of that developing a traditional html ui, a ruby backend, and ajax-ifying the application after being built. - i started straight off with a camping-based json api (for the model). - next step was writing the controller in pure js - no dom interactions here. - then finishing off with a view

I''ve been working with Camping for a little while, reading through the examples. The "Small Apps, Many Mounts" idea makes sense, and interacting with other apps'' models (using the full class name) works just as it should. But what is the best way to include links to other mounted applications? As a toy example, I''m trying to add links to the pages in the Tepee

So would you like this: $ wget http://rubyforge.org/gems/junebug-0.0.18.gem $ camping junebug-0.0.18.gem Or should it be: $ gem install junebug $ touch junebug.gemcamp $ camping junebug.gemcamp _why