Ohai chefs,
I just blogged about how to use Berkshelf to set up logstash, hope it is
useful to you!
Hey Bryan!
I'm glad you're taking a liking to Berkshelf and that it's working for your workflow! I had a few amendments to the Berkshelf portion of your post in the form of "best practices" that we have found while developing cookbooks.
The usage of the 'metadata' keyword in your Berksfile tells Berkshelf to look at the metadata.rb of your current working project for a list of dependencies. You want to lock version constraints in your metadata.rb and you do not need to define a source for cookbooks that you intend to retrieve from the Opscode site. If you are retrieving a cookbook that is not located at the Opscode site, and is located in Git or on you local disk, then you override it's location by placing a source in your file.
In this case you would not need to include the cookbook entries for apt, logrotate, vim, monit, nginx, or yum, since they are all found on the opscode site.
When you are installing your cookbooks with shims you need to make sure you don't place them within the path of a source that has a path location specified in your Berksfile. It's also important that you don't place the shims in a directory that already contains content.
There are a number of things we can do to make things more friendly and we're working on it. Thank you for bearing with us while we nail this all down.
--
Jamie Winsor
@resetexistence
On Monday, July 2, 2012 at 12:40 AM, Bryan Berry wrote:
Ohai chefs,
I just blogged about how to use Berkshelf to set up logstash, hope it is useful to you!
devopsanywhere: Stash those logs! Set up Logstash quickly with Chef + Berkshelf
Thanks for the tips Jamie, I will try to revise the blog post to account
for them
On Wed, Jul 4, 2012 at 1:04 AM, Jamie Winsor jamie@vialstudios.com wrote:
Hey Bryan!
I'm glad you're taking a liking to Berkshelf and that it's working for
your workflow! I had a few amendments to the Berkshelf portion of your post
in the form of "best practices" that we have found while developing
cookbooks.The usage of the 'metadata' keyword in your Berksfile tells Berkshelf to
look at the metadata.rb of your current working project for a list of
dependencies. You want to lock version constraints in your metadata.rb and
you do not need to define a source for cookbooks that you intend to
retrieve from the Opscode site. If you are retrieving a cookbook that is
not located at the Opscode site, and is located in Git or on you local
disk, then you override it's location by placing a source in your file.In this case you would not need to include the cookbook entries for apt,
logrotate, vim, monit, nginx, or yum, since they are all found on the
opscode site.When you are installing your cookbooks with shims you need to make sure
you don't place them within the path of a source that has a path location
specified in your Berksfile. It's also important that you don't place the
shims in a directory that already contains content.There are a number of things we can do to make things more friendly and
we're working on it. Thank you for bearing with us while we nail this all
down.--
Jamie Winsor
@resetexistence
reset (Jamie Stormbreaker) ยท GitHubOn Monday, July 2, 2012 at 12:40 AM, Bryan Berry wrote:
Ohai chefs,
I just blogged about how to use Berkshelf to set up logstash, hope it is
useful to you!devopsanywhere: Stash those logs! Set up Logstash quickly with Chef + Berkshelf