Berkshelf Workflow

1 · Seth Vargo · May 27, 2014, midnight
There are only two fundamental assumptions for working with Berkshelf: Each cookbook is a uniquely packaged and versioned artifact You have a centralized artifact store that exposes a dependency API and/or is indexable by the Berkshelf API Each cookbook is it own unit of infrastructure and should be treated as such. There are certainly situations where two or more cookbooks need to be iterated on in tandem, but those situations should be few and far between. In this article, I will discuss t...