discourse/chef/cookbooks/omnibus_updater/metadata.rb

name             "omnibus_updater"
maintainer       "Chris Roberts"
maintainer_email "chrisroberts.code@gmail.com"
license          "Apache 2.0"
description      "Chef omnibus package updater and installer"
long_description IO.read(File.join(File.dirname(__FILE__), 'README.md'))
version          "0.2.4"
Update the omnibus_updater chef recipe 2013-07-05 22:56:57 +08:00			`name "omnibus_updater"`
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-08 03:09:57 +08:00			`maintainer "Chris Roberts"`
			`maintainer_email "chrisroberts.code@gmail.com"`
			`license "Apache 2.0"`
			`description "Chef omnibus package updater and installer"`
			`long_description IO.read(File.join(File.dirname(__FILE__), 'README.md'))`
Update the omnibus_updater chef recipe 2013-07-05 22:56:57 +08:00			`version "0.2.4"`
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-08 03:09:57 +08:00