Re: What now?
Agreed, but ideally it would be great to have it updated as the dead links (redhanded.hobix.com, code.whytheluckystiff.net etc.) give the impression that Camping is neglected (also with the CHANGELOG frozen at 1.5 in 2006), and that's a bit sad for such a nice little framework! Perhaps the community could list and collate the necessary changes/updates on each page, then updating could be shared (I'd be more than willing to do updates)? An external website would be an extra to collect links and provide an overview, with - say - where get Camping, recent examples from the community, how-to guides (or links and previews), etc. all in one SEO- optimised place. Also, Camping does have some advantages over - say - Sinatra (one being that Sintra needs a reload with each code update) - these aren't immediately apparent unless pointed out. A few of the best Ruby Micro-frameworks deserve a fair hearing, and Camping isn't getting all the web presence it deserves - that's what motivates me! - Dave Everitt Awesome suggestion, but we let's not forget that camping.rubyforge.org has served us well :-) //Magnus Holm I second the whywentcamping.com domain. Dave: great, that's a start. One more person and we're there! Matt: I'm new to Camping (played around with some small apps, but nothing impressive), but I'd be more than happy to be webmaster. If I could get someone to work with, that'd be even better, of course. Dave: Nice alternative... all that's needed is a chosen domain, a friendly host and to share out the webmastering :-) With a little commitment from a couple of people, I'd provide the hosting and domain. ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: What now?
On 18 Oct 2009, at 12:03, Dave Everitt wrote: Perhaps the community could list and collate the necessary changes/ updates on each page, then updating could be shared (I'd be more than willing to do updates)? A new site shared over githubz would be nice. -- Julik Tarkhanov m...@julik.nl ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: What now?
I like the idea of updating the rubyforge site, but having a main site to publicize Camping would be a nice addition and would have the benefit of being easier for people to find or remember (especially if they are new to Ruby). I really like: * rubycamping.com * campingframework.com Here is an additional suggestion: rubyoncamping.com (like ROR). The new site could act as a portal for everything Camping, such as news, rotating features on sites using Camping, code snippets, etc. Philippe Dave Everitt wrote: Agreed, but ideally it would be great to have it updated as the dead links (redhanded.hobix.com, code.whytheluckystiff.net etc.) give the impression that Camping is neglected (also with the CHANGELOG frozen at 1.5 in 2006), and that's a bit sad for such a nice little framework! Perhaps the community could list and collate the necessary changes/updates on each page, then updating could be shared (I'd be more than willing to do updates)? An external website would be an extra to collect links and provide an overview, with - say - where get Camping, recent examples from the community, how-to guides (or links and previews), etc. all in one SEO-optimised place. Also, Camping does have some advantages over - say - Sinatra (one being that Sintra needs a reload with each code update) - these aren't immediately apparent unless pointed out. A few of the best Ruby Micro-frameworks deserve a fair hearing, and Camping isn't getting all the web presence it deserves - that's what motivates me! - Dave Everitt Awesome suggestion, but we let's not forget that camping.rubyforge.org has served us well :-) //Magnus Holm I second the whywentcamping.com domain. Dave: great, that's a start. One more person and we're there! Matt: I'm new to Camping (played around with some small apps, but nothing impressive), but I'd be more than happy to be webmaster. If I could get someone to work with, that'd be even better, of course. Dave: Nice alternative... all that's needed is a chosen domain, a friendly host and to share out the webmastering :-) With a little commitment from a couple of people, I'd provide the hosting and domain. ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: What now?
I like the domain whywentcamping.com . ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: What now?
@Philippe: Agreed - if Camping is going to get any mindshare it does need a portal one-stop site. BTW rubyoncamping - ROC (as in 'solid as a...' :-? ) So... .com/org/net(all?) domain options (bearing in mind SEO- friendliness and availability) - [ ] = add a score out of 10: rubycamping.com [ ] campingframework.com [ ] rubyoncamping.com [ ] whywentcamping.com [ ] Domains cost around £12 p.a., which I'm sure we can find between us. Hosting (I imagine with all the sysadmins and webmasters on this list ;-) is effectively free. @Julik: A new site shared over githubz would be nice You'll have heard that _why's inheritance already has a preservation plan (see 'Decentralization of _why's Projects' at http:// whymirror.github.com) - there's a lot of [planning|thinking|reporting on what's happening] there, and Magnus is already part-time 'scoutmaster' for Camping at http://github.com/camping/camping ... or did you mean something other? - Dave I like the idea of updating the rubyforge site, but having a main site to publicize Camping would be a nice addition and would have the benefit of being easier for people to find or remember (especially if they are new to Ruby). I really like: rubycamping.com campingframework.com Here is an additional suggestion: rubyoncamping.com (like ROR). The new site could act as a portal for everything Camping, such as news, rotating features on sites using Camping, code snippets, etc. Philippe Dave Everitt wrote: Agreed, but ideally it would be great to have it updated as the dead links (redhanded.hobix.com, code.whytheluckystiff.net etc.) give the impression that Camping is neglected (also with the CHANGELOG frozen at 1.5 in 2006), and that's a bit sad for such a nice little framework! Perhaps the community could list and collate the necessary changes/updates on each page, then updating could be shared (I'd be more than willing to do updates)? An external website would be an extra to collect links and provide an overview, with - say - where get Camping, recent examples from the community, how-to guides (or links and previews), etc. all in one SEO-optimised place. Also, Camping does have some advantages over - say - Sinatra (one being that Sintra needs a reload with each code update) - these aren't immediately apparent unless pointed out. A few of the best Ruby Micro-frameworks deserve a fair hearing, and Camping isn't getting all the web presence it deserves - that's what motivates me! - Dave Everitt ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Camping sessions issue (and fix?) when mounting multiple apps
Hi all, Not sure where best to raise this (github issues?) but I'm seeing an issue with the cookie sessions in camping 2.0 using rack. If I mount an app such as the example blog or the sessions test app at any url that is not the root session information is lost in some cases. Same thing happens if I use the built in Camping server. For example if I mount the blog app using rackup at '/blog' I'm unable to log in. If I mount the sessions test app the information added on the second page is lost when it reaches page three. Looking at the cookies in the browser I can see two state cookies set with the paths '/' and '/blog/'. I'm guessing this is to do with Rack::Session::Cookie in session.rb, which will default to use :path = '/' in all cases. If I explicitly add :path = '/blog/' there it starts working as expected. Some more detailed outputs here (this will run from /test) http://pastebin.com/m6c13a4aa Is that me doing something crazy there (I'm not expert!) or is that a bug? If that's an issue I think the below change to session.rb fixes it, passing in the apps @root into the path Rack's session cookie middleware. I can push that somewhere if we reckon that's a fix? - app.use Rack::Session::Cookie, :key = key, :secret = secret + app.use Rack::Session::Cookie, :key = key, :secret = secret, :path = @root Regards, Jon ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: What now?
+1 for whywentcamping.com ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: What now?
I need to know if _why is OK, I need a sign? 2009/10/18 zimbatm zimb...@oree.ch: +1 for whywentcamping.com ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: What now?
Another for whywentcamping.com We shouldn't try and make ourselves look like ROR, Camping is it's own crazy system. Christian Carter 612.327.5292 On Sun, Oct 18, 2009 at 3:53 PM, zimbatm zimb...@oree.ch wrote: +1 for whywentcamping.com ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Camping sessions issue (and fix?) when mounting multiple apps
Wow, great catch! This is definitely a bug. I guess this should go to
GitHub issues, yes.
This is actually an issue where Camping and Rack::Session::Cookie fight:
At the first request, sessions.state is set in ::Cookie after Camping
has done its magic.
At the second request, Camping loads @state from @env['rack.state'],
the app changes the session, but @cookie['sessions.state'] stays
intact. Camping's #to_a then sets the cookies again in the response:
@cookies.each do |k, v|
v = {:value = v, :path = self / /} if String === v
r.set_cookie(k, v)
end
Which means that it sets a sessions.state-cookie at /sessions/. Then
::Cookies kicks in and figures out that the sessions have changed and
sets a new cookie, but this time at /. (This also has the effect that
Camping copies all the cookies at / into /sessions/)
At the third request, Rack chooses cookies such that those with more
specific Path attributes precede those with less specific, and the
cookie at /sessions/ wins.
Your fix won't unfornately work because @root is only available inside
a request/controller.
I think we need to do two things:
* Make sure Camping only sets cookies when they've changed.
* Figure out a way to set :path to SCRIPT_NAME. If so, this should
only be an option, as you might also want to mount two apps and have
them share the sessions (aka :path = '/').
I'm not quite sure how we should add that option, though. We could
switch Camping::Session to be a middleware, but this means all apps
will have to change include Camping::Session to use
Camping::Session. It's maybe not such a big deal? We should at least
do these kind of changes *before* the release of 2.0.
Some examples:
# Middleware
use Camping::Session, :secret = foo, :shared = true
# Subclass
include Camping::Session::Shared
secret foo
# New method
include Camping::Session
secret foo
shared_cookie!
# Merge #secret and #shared_cookie! together
include Camping::Session
session_options :secret = foo, :shared = true
I think I actually prefer the middleware-version. It's short and
concise and can be extended with more options if needed.
What do you think?
//Magnus Holm
On Sun, Oct 18, 2009 at 19:59, Jonathan Hickford
jonathan.hickford+camp...@gmail.com wrote:
Hi all,
Not sure where best to raise this (github issues?) but I'm seeing an
issue with the cookie sessions in camping 2.0 using rack. If I mount
an app such as the example blog or the sessions test app at any url
that is not the root session information is lost in some cases. Same
thing happens if I use the built in Camping server.
For example if I mount the blog app using rackup at '/blog' I'm unable
to log in. If I mount the sessions test app the information added on
the second page is lost when it reaches page three. Looking at the
cookies in the browser I can see two state cookies set with the paths
'/' and '/blog/'.
I'm guessing this is to do with Rack::Session::Cookie in session.rb,
which will default to use :path = '/' in all cases. If I explicitly
add :path = '/blog/' there it starts working as expected. Some more
detailed outputs here (this will run from /test)
http://pastebin.com/m6c13a4aa
Is that me doing something crazy there (I'm not expert!) or is that a
bug? If that's an issue I think the below change to session.rb fixes
it, passing in the apps @root into the path Rack's session cookie
middleware. I can push that somewhere if we reckon that's a fix?
- app.use Rack::Session::Cookie, :key = key, :secret = secret
+ app.use Rack::Session::Cookie, :key = key, :secret = secret, :path =
@root
Regards,
Jon
___
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list
___
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list
Re: What should the portal-site contain?
Magnus hope you don't mind but for now, I took the liberty of adding most of these links to the wiki. BTW I use the mail archive pages at mail- archive.com - easier to browse than the standard interface. Anything you don't want on the wiki right now, please just remove. But otherwise, it will be a good test of how handy the 'one-stop' thing might be. For now, that's all for the next few days from me - I have some annoying paid work to do this week. Dave Source: http://github.com/camping/camping Mailing list: rubyforge.org/something/I-always-google Bugs: http://github.com/camping/camping/issues Wiki: http://wiki.github.com/camping/camping Docs: http://camping.rubyforge.org/ Book: http://camping.rubyforge.org/book.html (not yet, but hopefully soon) README: http://stuff.judofyr.net/camping-docs/ Reference: http://stuff.judofyr.net/camping-docs/api.html Book: http://stuff.judofyr.net/camping-docs/book.html ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
