Search results for chef

rubygem-knife-cloudstack-fog-0.6.0-1.lbn19.noarch

Support for the Chef Knife command, leveraging FOG, for the Apache CloudStack / Citrix CloudPlatform API

rubygem-knife-cloudstack-fog-0.6.0-1.lbn25.noarch

Support for the Chef Knife command, leveraging FOG, for the Apache CloudStack / Citrix CloudPlatform API.

rubygem-knife-container-0.2.4-1.lbn19.noarch

This is the official Chef plugin for Linux Containers. This plugin gives knife the ability to initialize and build Linux Containers. For full documentation, including examples, please check out the docs site. Subcommands This plugin provides the following Knife subcommands. Specific command options can be found by invoking the subcommand with a --help flag. knife container docker init Initializes a new folder that will hold all the files and folders necessary to build a Docker image called a “Docker context.” This files and folders that can make up your Docker context include a Dockerfile, Berksfile, cookbooks and chef-client configuration files. knife container docker build Builds a Docker image based on the Docker context specified. If the image was initialized using the -z flag and a Berksfile exists, it will run berks vendor and vendor the required cookbooks into the required directory. If the image was initialized without the -z flag and a Berksfile exists, it will run berks upload and upload the required cookbooks to you Chef Server.

rubygem-knife-essentials-1.5.3-2.lbn13.noarch

knife-essentials provides a number of useful knife commands that allow you to manipulate Chef using a common set of verbs that work on everything that is stored in the Chef server. knife diff cookbooks/*apache* knife download roles data_bags cookbooks/emacs knife upload apache* knife list data_bags/users knife deps roles/base.json cd cookbooks && knife show *base* More verbs will be added as time goes by. PRINCIPLES * Unified commands that work on everything knife-essentials thinks verbs come first. There are only a few things you need to do with pretty much everything in the system: you upload them, download them, look at them, edit them, list them, diff them, and delete then. knife-essentials provides a number of verb commands: +knife diff roles+ and +knife list roles+ among them. These commands work on all types of objects, as well. You can type +knife diff roles+, or +knife diff data_bags/users/jkeiser.json+. * Treat the Chef server is like your filesystem knife-essentials treats the Chef server like a mirror of a Chef repository. Most of the stuff you do with the Chef Server is based on your local repository–a set of files in directories like roles, data_bags, cookbooks, etc. The Chef Server has objects that match them–in fact, you can upload and download the files on your filesystem to change the file server. This makes learning the knife commands easy, and makes important commands like diff, upload and download extremely simple to do and easy to understand. * Take context into account When you’re in the roles directory, the system knows that’s what you are working with. Just type +knife show base.json+ and it will show you the base role from the server. knife-essentials knows.

rubygem-knife-essentials-1.5.3-2.lbn19.noarch

knife-essentials provides a number of useful knife commands that allow you to manipulate Chef using a common set of verbs that work on everything that is stored in the Chef server. knife diff cookbooks/*apache* knife download roles data_bags cookbooks/emacs knife upload apache* knife list data_bags/users knife deps roles/base.json cd cookbooks && knife show *base* More verbs will be added as time goes by. PRINCIPLES * Unified commands that work on everything knife-essentials thinks verbs come first. There are only a few things you need to do with pretty much everything in the system: you upload them, download them, look at them, edit them, list them, diff them, and delete then. knife-essentials provides a number of verb commands: +knife diff roles+ and +knife list roles+ among them. These commands work on all types of objects, as well. You can type +knife diff roles+, or +knife diff data_bags/users/jkeiser.json+. * Treat the Chef server is like your filesystem knife-essentials treats the Chef server like a mirror of a Chef repository. Most of the stuff you do with the Chef Server is based on your local repository–a set of files in directories like roles, data_bags, cookbooks, etc. The Chef Server has objects that match them–in fact, you can upload and download the files on your filesystem to change the file server. This makes learning the knife commands easy, and makes important commands like diff, upload and download extremely simple to do and easy to understand. * Take context into account When you’re in the roles directory, the system knows that’s what you are working with. Just type +knife show base.json+ and it will show you the base role from the server. knife-essentials knows.

rubygem-knife-essentials-1.5.6-1.lbn25.noarch

Universal knife verbs that work with your Chef repository.

rubygem-knife-foodcritic-0.2.1-1.lbn19.noarch

Knife-Foodcritic is a plugin for Chef::Knife which automatically generates a new rule file (with an optional description), example spec files and a cookbook to test the rule against. It also generates the spec_helper if it doesn't already exist.

rubygem-knife-foodcritic-0.2.1-1.lbn25.noarch

Knife-Foodcritic is a plugin for Chef::Knife which automatically generates a new rule file (with an optional description), example spec files and a cookbook to test the rule against. It also generates the spec_helper if it doesn't already exist.

rubygem-knife-ghost-0.1.0-1.lbn13.noarch

Automatically populates /etc/hosts with node domain names and IP addresses from Chef, requires sudo privileges to edit /etc/hosts

rubygem-knife-ghost-0.1.0-1.lbn19.noarch

Automatically populates /etc/hosts with node domain names and IP addresses from Chef, requires sudo privileges to edit /etc/hosts