Managing your ey-cloud-recipes

August 26, 2010 Mike Barinek

If you’ve recently forked the ey-cloud-recipes on GitHub and then had issues
managing and deploying multiple projects with disparate dependencies using the
single forked gem, then we have a solution that has worked well on a recent project.

We’ve tucked the cookbooks directory underneath our Rails project. To apply Chef
changes, we installed the ‘engineyard’ gem and us ‘ey recipes upload’ and
‘ey recipes apply’ from within our Rails project.

Upside, everything you need to know about the project is local to the project.


.
├── Gemfile
├── Gemfile.lock
├── README.md
├── Rakefile
├── app
├── cookbooks
│   ├── main
│   │   ├── attributes
│   │   │   └── recipe.rb
│   │   ├── definitions
│   │   │   └── ey_cloud_report.rb
│   │   ├── libraries
│   │   │   ├── ruby_block.rb
│   │   │   └── run_for_app.rb
│   │   └── recipes
│   │       └── default.rb
│   ├── redis
│   │   ├── README.rdoc
│   │   ├── recipes
│   │   │   └── default.rb
│   │   └── templates
│   │       └── default
│   │           ├── redis.conf.erb
│   │           └── redis.monitrc.erb
│   └── sunspot
│       ├── recipes
│       │   └── default.rb
│       └── templates
│           └── default
│               ├── solr.erb
│               └── solr.monitrc.erb

About the Author

Biography

More Content by Mike Barinek
Previous
Ruby Enumerable and string
Ruby Enumerable and string

Did you know that you can call map() and each() on a Ruby string? Do you know how they behave? I hope I'm...

Next
New Tech Talk: Diaspora
New Tech Talk: Diaspora

Maxwell Salzberg and Raphael Sofaer, two of the four founders of Diaspora, discuss the privacy aware, perso...

Enter curious. Exit smarter.

Register Now