discourse/chef/cookbooks/omnibus_updater/attributes/default.rb

default[:omnibus_updater][:version] = '10.18.2'
default[:omnibus_updater][:version_search] = false
default[:omnibus_updater][:base_uri] = 'http://opscode-omnitruck-release.s3.amazonaws.com'
default[:omnibus_updater][:cache_dir] = '/opt'
default[:omnibus_updater][:cache_omnibus_installer] = false
default[:omnibus_updater][:remove_chef_system_gem] = false
default[:omnibus_updater][:allow_release_clients] = false
default[:omnibus_updater][:disabled] = false
Use chef-solo to install phantomjs into Vagrant VM. This introduces two configuration management runs into the Vagrant provisioning phase. The first chef-solo run ensures that a current version of chef is installed using the omnibus updater. The second chef-solo run installs vim and phantomjs. Much more is possible, this is a proof of concept. Cookbooks are stored in the chef directory, and managed by librarian-chef, which is like a bundler for cookbooks. Chef is run when VM is first downloaded and booted, but not on subsequent halt/up cycles. To force chef to run again, use `vagrant provision`. 2013-02-07 14:09:57 -05:00			`default[:omnibus_updater][:version] = '10.18.2'`
			`default[:omnibus_updater][:version_search] = false`
			`default[:omnibus_updater][:base_uri] = 'http://opscode-omnitruck-release.s3.amazonaws.com'`
			`default[:omnibus_updater][:cache_dir] = '/opt'`
			`default[:omnibus_updater][:cache_omnibus_installer] = false`
			`default[:omnibus_updater][:remove_chef_system_gem] = false`
			`default[:omnibus_updater][:allow_release_clients] = false`
			`default[:omnibus_updater][:disabled] = false`