[chef] Re: Re: kitchen, hideabed

[Matthew Todd <matthew.todd@gmail.com>]

On Jul 7, 2009, at 12:55 AM, Adam Jacob wrote:

> > On a yak-shaving whim, I've gone and bundled up chef-server-slice  
> > such that
> > it can be run on Heroku:
> >
> >  http://github.com/matthewtodd/kitchen

Note: I'll be changing the name shortly, due to a collision I hadn't  
been aware of. I'll post the updated link here when I do.

> > 2. There are some monkey-patches in the project I'm hoping to  
> > integrate back
> > into Chef proper, most notably support for HTTP basic  
> > authentication in
> > Chef::REST.
>
> Would love it - have you opened feature tickets yet?

Just now:

Add support for HTTP Basic Authentication to Chef::REST
http://tickets.opscode.com/browse/CHEF-430

ChefServerSlice::OpenidServer#index should treat content_type as a  
symbol
http://tickets.opscode.com/browse/CHEF-431

chef-server-slice views should use slice_url instead of url
http://tickets.opscode.com/browse/CHEF-432

> > 3. I've written my own OpenID::Store::CouchDB, as I had a little  
> > difficulty
> > with the one on github. (Though, if I understand
> > http://lists.opscode.com/sympa/arc/chef-dev/2009-06/msg00001.html,  
> > it's got
> > a short lifetime of usefulness anyway.)
>
> Cool - are you planning on releasing it?

I had planned to keep it bundled with the Rack app, as it  
(expediently) uses Chef::CouchDB and is thus not *really* a pure  
CouchDB store for OpenID.*

Though perhaps it would make sense to create an "openid-store-couchdb- 
chef" gem that still provided for "require 'openid-store-couchdb'"?

Please advise!

Cheers,  -- Matthew


* Note that this also means "associations" and "nonces" live in the  
chef database, rather than as top-level databases of their own. So  
the databases created in ChefServerSlice.loaded go unused.