On Tue, Dec 6, 2011 at 12:34 PM, Brad Knowles firstname.lastname@example.org wrote:
I would think that you should be able to do an install using the “full-stack chef-client installer” from the omnibus build system, and then from there proceed on to getting the rest of the chef-server stuff built. At least, that would save you a certain amount of work.
I would recommend against that.
For starters, it is hard for anyone to support or help you if you have
problems, because you’re doing it in a unique way. If you follow the
documented directions and run into an issue because of something
special about your setup, it is more likely that someone else would
have made the same mistake and you’ll be able to find their notes or
Further though, Omnibus Client installs to an isolated part of the
system. For instance, it comes with its own known-working version of
ruby that won’t interfere with another version of ruby installed on
the system. Installing the Omnibus client and the chef server some
other way will mean that you’ve got the server and client working on
different ruby stacks, and you’ll have multiple installs of rubygems,
including multiple versions of the chef gems installed.
Using the Chef-solo install is pretty easy if you’ve got ruby because
it uses Chef-solo to set up the server for you, with init scripts. If
you have any experience with rubygems, it’s the easiest path.