- From: Matthew Todd <matthew.todd@gmail.com>
- To: chef@lists.opscode.com
- Subject: [chef] kitchen, hideabed
- Date: Mon, 6 Jul 2009 18:18:30 +0300
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:content-transfer-encoding:message-id:content-type:to :from:subject:date:x-mailer; b=cUslGe+ZmMigcMZ5eki3e3PCqcxu9jLTXQgOUgeKusCeba8QHYORi+5SFxYehtUH95 VBqfJtSOxIP3tRbZjCVlCPWrylYEY6Roje9Pf9USaHmdsS8zzkxnDLJREFkDHbcQRHyq YU7BygVljuOTtrQFf3cmWFt2VucES4JIbzZYE=
Hi, all --
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
If happen to give it a try, I'd love your ideas / feedback / patches.
Interested readers will note that:
1. Chef::Queue is stubbed out for now. So recipes that need search
won't work.
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.
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.)
On a related note, since CouchDB isn't available on Heroku, I've
written up a small Rails app that looks just enough like CouchDB to
get Chef to work:
http://github.com/matthewtodd/hideabed
Granted, this flies in the face of everything CouchDB stands for, but
it's also a simple way to get a toy server up and running for my 3
Chef clients. :-)
Patches welcome,
-- Matthew
- [chef] kitchen, hideabed, Matthew Todd, 07/06/2009
Archive powered by MHonArc 2.6.16.