similar to: throw :halt

You''ll need to install the ''openid'' gem for this, and require it in your camping app: class Login < R ''/login'' def get this_url = ''http:'' + URL(''/login'').to_s unless input.finish.to_s == ''1'' # start doing the auth here begin

I''ve just sent a pull-request to _why with my changes[1] and here is some things that I think needs to be done before a (possible) release: * The cookie session is named Camping::Session and is placed in camping/session.rb. Maybe this should be called Camping::CookieSession or??? * The ActiveRecord session is named Camping::ARSession and is placed in camping/ar/session.rb. Maybe it

Anyone knows if we still need to follow the instructions at http://web.archive.org/web/20080113055731/code.whytheluckystiff.net/camping/wiki/BeAlertWhenOnSqlite3, or if the stable release is good enough? //Magnus Holm -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/camping-list/attachments/20090124/c31af77a/attachment.html>

I was having some issue getting the class variables in Camping::Session to work with some old apps, so I''ve changed @@state_secret to a method. module Blog include Camping::Session def state_secret; "kxxxx" end end Also, merged some of zimbatm''s patches. And trying to revive the Junebug wiki <http://github.com/why/junebug> since it''s still

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

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

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)

=== 1. Camping on Rack === I''ve just finished rewriting Camping to use Rack in the "core". I got rid of (a little less) than 1kB in camping.rb and removed lots of un-necessary files (lib/server/*.rb, fastcgi.rb & mongrel.rb). bin/camping does now only provide WEBrick, Mongrel and console-support and should only be used in development. It uses Rack::ShowExceptions to catch

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

It looks like everyone has tried to fix the cookies lately, and no-one managed to get it 100% correctly. The current implementation doesn''t set the path correctly, and you can''t use @cookies in a #service-overload. Qwzybug''s patch fixed only the sessions. Jenna''s patch won''t allow to set complex cookies (@cookies.key = {:path => "/path",

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

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

Hi all I found the Camping page on Wikipedia in need of some serious TLC, so I updated it, added some newer links and removed the ''stub'' status: http://en.wikipedia.org/wiki/Camping_%28microframework%29 I also pointed people to the Github repo for version 1.9. Please take a look and either make suggestions for further material for me to add (not too much...

Okay, Camping 1.4 is out. gem install camping --source code.whytheluckystiff.net The only recent change is that the request body gets store in the @in variable as an open stream. It''s also okay to pass an IO object out of Camping. Lastly, Camping + Mongrel (SVN) now supports the X-Sendfile header. [1] Very swift and cool. _why [1]

Oh, by the way, gem announcements are now listed on the feeds. So, if you want to follow camping development and get feed announcements as well, the feed for you is: <http://code.whytheluckystiff.net/camping.xml> Or if you want all checkins and gem releases for the entire repo: <http://code.whytheluckystiff.net/index.xml> Every project in the repository has a feed, so

Hello all, Recently I have started writing some small package apps. The main app I''m working on at the moment is Camping/Photos[1]. Here I use a controller to serve static files (Theme[3]) that I have copied from [2]. There seems a problem however, when using this via lighttpd. All files that get served (via photos-dispatch.rb) get an extra ''\r\n'' in front. This

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,

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

Just a few minor changes released before I add gem support. * R() now accepts a Hash in its arguments which can be used to build a query string. R(Topic, @topic.id, :page => 24) #=> "/topic/14?page=24" * Base#to_a, discussed here.[1] Can be used to forward requests. Both the camping and camping-omnibus gems are fresh. gem install camping-omnibus --source