Project
Reverse Dependencies for chef
The projects listed here declare chef as a runtime or development dependency
0.02
Xen API Support for Chef's Knife Command
2020
2021
2022
2023
2024
2025
0.02
A Bundler for your Chef Cookbooks.
2020
2021
2022
2023
2024
2025
0.02
Client for Chef push jobs server
2020
2021
2022
2023
2024
2025
0.02
A Chef cookbook for unpacking file archives like tar and zip.
2020
2021
2022
2023
2024
2025
0.02
A Chef cookbook to help writing language cookbooks.
2020
2021
2022
2023
2024
2025
0.02
A Chef cookbook for managing the Monit process manager.
2020
2021
2022
2023
2024
2025
0.02
A Chef cookbook for managing Ruby installations.
2020
2021
2022
2023
2024
2025
0.01
Extenstions for berkshelf
2020
2021
2022
2023
2024
2025
0.01
Allows Capistrano to use Chef data for deployment
2020
2021
2022
2023
2024
2025
0.01
Define, enforce, and handle violations of validation rules for Chef node attributes. This gem provides the validation engine, and can be used outside of a convergence run; a cookbook (attribute-validator) is available to perform validation during a chef run, at compile or converge time.
2020
2021
2022
2023
2024
2025
0.01
Chef-Berksfile-Env
==================
A Chef plugin which allows you to lock down your Chef Environment's cookbook versions with a Berksfile.
This is effectively the same as doing `berks apply ...` but via `knife environment from file ...`.
View the [Change Log](https://github.com/bbaugher/che...
2020
2021
2022
2023
2024
2025
0.01
This library adds the `container_init` Chef resource. Using this resource allows you to hijack service resources and use the runit installation included with chef-container.
2020
2021
2022
2023
2024
2025
0.01
A streamlined development and deployment workflow for Chef platform.
2020
2021
2022
2023
2024
2025
0.01
Low level manipulation tool for Chef Infra Server
2020
2021
2022
2023
2024
2025
0.01
Low level manipulation tool for Chef Server 12 and later
2020
2021
2022
2023
2024
2025
0.01
= DESCRIPTION:
Provides a Chef handler which can report run status, including any changes that were made, to a Graylog2 server. In the case of failed runs a backtrace will be included in the details reported.
= REQUIREMENTS:
* A Graylog2 server running somewhere.
= USAGE:
This example makes ...
2020
2021
2022
2023
2024
2025
0.01
Push reporting stats to Librato metrics
2020
2021
2022
2023
2024
2025
0.01
Chef report handler for sending run detail information to Opsmatic
2020
2021
2022
2023
2024
2025