- From: Dennis <
- To: "
- Subject: [chef-dev] cookbook vs gem
- Date: Thu, 8 May 2014 13:51:34 +0200
- Openpgp: url=http://pool.sks-keyservers.net/pks/lookup?op=get&search=0xF08E4407
the design decision I love most about chef is that one has the full featured
ruby language at
hand. The main method of packaging and distributing ruby chef code is via
cookbooks - one could
think of them as chef code libraries, so in fact a subset of generic ruby
libraries. The most
important tools to manage our cookbooks are some SCM like git and berkshelf.
Berkshelf looks very
similar to bundler.
Up to now I could not answer myself the question: Why are cookbooks different
People are developing cookbook repository servers with indexes,
state-of-the-art APIs and all that
cool stuff. As I understand, there are not any good solutions to mirror the
official or even host
your own gem repository. What about features like signed cookbooks/gems? My
point is, I have a
strong feeling we could benefit from collaboration with the rubygems project
(and vice versa).
I would claim that the most important features of our cookbook stack overlaps
with gems and it
feels to me like reinventing the wheel just because it is perceived as
seperate domains of
I am writing to this list to ask you, if I am missing a major point?! Is
anyone aware of
discussions, articles, projects or efforts on consolidating cookbooks and
I greatly appreciate your feedback!
- [chef-dev] cookbook vs gem, Dennis, 05/08/2014
Archive powered by MHonArc 2.6.16.