[chef] Re: Re: Re: Re: Re: Omnibus installer doesn't create /etc/chef?

[Bryan Berry < >]

afaik the default template doesn't use omnibus, however I haven't looked at it in a long time

I need to delete that damn fprintd cuz it sends lots of annoying e-mails about not being able to connect to a fingerprint reader.

On Wed, Jun 27, 2012 at 1:49 PM, Jeremiah Snapp < " target="_blank"> > wrote:

Thanks Bryan.  I'm curious, is there anything wrong with the default template for RHEL 6.2?  Or are you just creating your own template to accomplish your customizations?

On Wed, Jun 27, 2012 at 7:22 AM, Bryan Berry < " target="_blank"> > wrote:

Jeremiah, here is my bootstrap template in a gist for RHEL 6.2 using omnibus 6.2

https://gist.github.com/2948410 

On Wed, Jun 27, 2012 at 1:17 PM, Jeremiah Snapp < " target="_blank"> > wrote:

Thanks for the excellent explanation.  That makes total sense.

Jeremiah

On Tue, Jun 26, 2012 at 10:18 AM, Bryan McLellan < " target="_blank"> > wrote:

There are many ways the /etc/chef directory gets created and it's
always when chef is being configured.

'knife bootstrap' will create the appropriate directories over ssh or winrm.

The debian packaging configures the client using debconf and will
create the appropriate directories.

On Tue, Jun 26, 2012 at 7:43 AM, Jeremiah Snapp
< " target="_blank"> > wrote:

> When I use the omnibus chef-client installer on Ubuntu 12.04 it doesn't
> create the /etc/chef directory.  Is that normal?  It seems like it should
> create it for you.

Omnibus creates /etc/chef when you configure Chef using

/opt/chef/setup.sh -v validation_key -o hosted_chef organization
/opt/chef/setup.sh -v validation_key -u http://chef_server.example.org

On Tue, Jun 26, 2012 at 7:51 AM, Jeremiah Snapp
< " target="_blank"> > wrote:
> I also just installed chef via ruby gems and it didn't create /etc/chef
> either.  Can that directory be added to the chef-client install procedures
> as a default?

As a packaging system, Rubygems isn't really designed for complete
application configuration. Since we aren't going to do the
configuration, it is presumptuous to  create a directory that may not
be used. This action may also make it harder to do the correct thing
in other packaging systems that base off of the Rubygem.

Bryan