[chef] Re: Chef repository usage...

[AJ Christensen < >]

I'd suggest forking the opscode/chef-repo repository and building up
from there. Use knife to upload the contents of the chef-repo to the
chef-server (hosted chef or otherwise), or to drive an chef-solo
configuration (maybe with Vagrant)

Some tools to investigate that may assist:

* Vagrant - http://vagrantup.com/
* Librarian - https://github.com/applicationsonline/librarian
* Berkshelf - https://github.com/RiotGames/berkshelf
* guard-knife - https://github.com/nistude/guard-knife
* knife-table - https://github.com/heavywater/knife-table
* knife-spork - https://github.com/jonlives/knife-spork

Cheers,

--AJ

On 23 July 2012 16:54, Morgan Blackthorne 
<
 >
 wrote:
> Still getting up to speed with chef. I know that most people suggest putting
> the Chef configuration into a VCS like SVN/Git/etc, but what I'm not clear
> about is what files should be put into the repo and uploaded (say with shef
> or knife) and what should only exist on the chef server. For day to day
> operations, do you suggest using shef to edit and test configurations, and
> then download the files into the VCS repo to archive, or should everything
> be done through the VCS repo and pushed to the chef server via knife for
> testing?
>
> Is there a knife command that will take a full (properly formatted)
> directory structure and upload it to chef in one go, or do you have to
> upload everything individually?
>
> Thanks for the help.
>
> ~*~ StormeRider ~*~
>
> "With hearts immortal, we stand before our lives
> A soul against oblivion, forever asking why
> This upside down symphony in a paradox called life
> Our hearts immortal
> What you give to love, will never die"