search

hellofuture / gettingstartedwithchef

Getting started with Chef website
http://gettingstartedwithchef.com/
18 stars 3 forks source link

knife cookbook install [cookbook] #2

Closed drolfe closed 11 years ago

drolfe commented 11 years ago

Thought I would make the suggestion to use knife cookbook install rather then download as it with extract into your cookbooks directly without you having to work with the tar.gz

salgo commented 11 years ago

Hi, thanks for the suggestion.

I deliberately didn't use knife cookbook install as I thought it was all a bit magic. It's okay if you understand what it does but for your first play with Chef - as this is only the first chapter - I thought it might be good to show where the cookbooks come from.

The idea we had is that future chapters will slowly introduce a better way of working, while the early chapters do things in a more obvious and easy to follow way.

If the general consensus is that knife cookbook install is more obvious and easy to follow then I'll happily change it of course.

drolfe commented 11 years ago

That's all good. I'm new to chef and thought I was onto something :-).

I've been looking for a good howto for multi-node app deployments, it's very confusing for people new to chef as how to use attributes or data bags to pull for example MySQL server ip and database details if you wanted to have separation of services like one MySQL server for many nodes running different we apps. Hope your site will eventually cover these topics also

Regards Daniel

Sent from my iPhone

On 13/05/2013, at 6:55 PM, salgo notifications@github.com wrote:

Hi, thanks for the suggestion.

I deliberately didn't use knife cookbook install as I thought it was all a bit magic. It's okay if you understand what it does but for your first play with Chef - as this is only the first chapter - I thought it might be good to show where the cookbooks come from.

The idea we had is that future chapters will slowly introduce a better way of working, while the early chapters do things in a more obvious and easy to follow way.

If the general consensus is that knife cookbook install is more obvious and easy to follow then I'll happily change it of course.

— Reply to this email directly or view it on GitHub.

mattray commented 11 years ago

I'd made the same decision to use knife cookbook download with Spiceweasel to hide the git behavior unless explicitly chosen. @drolfe You may want to check out Spiceweasel for multi-node application deployments, it was written to help fill the gap between the code in the Chef repository and how everything ties together and is deployed.

charlesjohnson commented 11 years ago

Agreed with Matt, the knife cookbook install command and the git branch behavior is a little hand-wavey. I prefer download + unpack.

(Longer-term, this seems ripe for refactor, since the branch-per-cookbook repo model hasn't proven out with the community.)

salgo commented 11 years ago

I'm closing this then as everyone seems in some agreement.