For workstations, chefdk + knife-block (currently needing to be hand-patched to work with Chef 12) is probably the easiest way to get bootstrapped.--~*~ StormeRider ~*~"Every world needs its heroes [...] They inspire us to be better than we are. And they protect from the darkness that's just around the corner."(from Smallville Season 6x1: "Zod")
On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSSOn Mon, Feb 9, 2015 at 10:41 AM, Douglas Garstang < " target="_blank"> > wrote:Doesn't look like it's designed for use with multiple chef servers. :(--On Mon, Feb 9, 2015 at 10:19 AM, JJ Asghar < " target="_blank"> > wrote:I think the way to go is: https://github.com/chef/pantry-chef-repo
I personally haven't given it a shot yet but i know jtimberman has
some opinions :).
Best Regards,
JJ Asghar
c: 512.619.0722 t: @jjasghar irc: j^2
On Mon, Feb 9, 2015 at 11:09 AM, Douglas Garstang
< " target="_blank"> > wrote:
> So, I'm sitting here on a Monday morning (re)writing docs on how to install
> the chef client and configure it for our environment. I work for a startup,
> so this evolves (and sometimes devolves) frequently. I've had to rework this
> document a number of times, as you'd expect. There's gotta be a better way.
>
> Would writing a chef-solo recipe to configure someone's local system to set
> up the chef client be a more scalable solution? Anyone done this?
>
> Doug
>
Regards,
Douglas Garstang
http://www.linkedin.com/in/garstang
Email: " target="_blank">
Cell: +1-805-340-5627
Archive powered by MHonArc 2.6.16.