similar to: Do we still need to be alert when on SQLite3?

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

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

Greetings: I am using Sqlite3 database with my Rails app. When I try and run "rake tests" for the app it always fails with the error: ** Invoke default (first_time) ** Invoke test (first_time) ** Execute test ** Invoke test:units (first_time) ** Invoke db:test:prepare (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute db:test:prepare ** Invoke

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

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

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

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

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

Hello, I experienced a weird bug today, while implementing an AtomPub server. I pasted all the story and bug details here : http://p.caboo.se/110125 It maybe be related to http://code.whytheluckystiff.net/camping/ticket/142 ... I am using - mongrel 1.0.1 - camping 1.5 Cheers, -- Simon Rozet <simon at rozet.name>

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

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

This is the last time I try to fix something in the middle of the night! Feel free to call me a Stupid Snake, ''cause this has been messy. Anyway, I think I''ve finally solved this. Here it is: http://pastie.org/237138 :-) -- Magnus Holm

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

hi all, I''m looking for someone framiliar with the rails (and AWS) codebase to explain to me how exactly AWS connects to Rails. I''m asking because I want to hook in AWS to Camping (http://code.whytheluckystiff.net/camping) Thanks in advance! --Jesse -- Posted via http://www.ruby-forum.com/.

I''m trying to use Camping from Magnus'' repo (1.9.300) but running the blog.rb example (or anything for that matter) gives me Rack::Lint::LintError at / Content-Length header was 0, but should be 548 Ruby C:/ruby-1.8.7/lib/ruby/gems/1.8/gems/rack-0.9.1/lib/rack/lint.rb: in assert, line 16 Web GET localhost/ There are no errors on the camping output so I suspect something has

I tried to install RedCloth-3.274 in jruby (trunk) but the install failed when RedCloth tried to build the C code using mkmf: I forget whether SuperRedcloth ever did build in JRuby?? I know Hpricot (which also uses ragel which can compile to Java code) works in JRuby -- with the patch here: https://code.whytheluckystiff.net/hpricot/ticket/131) I might be confusing the two ... FYI: If you

what is the cleanest way to do something for every request of a particular type (Verb, and Content-Type header)? i''m trying to figure out if shipping a custom camping.rb is avoidable, and if, how i should structure a patch my app http://whats-your.name/yard/ uses exclusively JSON based messaging between server and client. this means POST bodies are JSON, and not querystring.. camping

Just ran into a problem[1]. It seems to have been introduced by changeset 224 [2], a fix for ticket 126 [3]. The root is the number of CRLFs Camping puts between the headers and the body of the response. This has changed at least 3 times; right now we''re back to 1. (ie. every header ends in a CRLF, and then there''s the body) The HTTP RFC[4], the CGI spec[5] and the FastCGI

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