Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

Select Status


beef (6) Versions 0.3.0

Installs/Configures BeEF

cookbook 'beef', '= 0.3.0', :supermarket
cookbook 'beef', '= 0.3.0'
knife supermarket install beef
knife supermarket download beef
Quality 100%

BeEF Cookbook

Install and configures BeFF - The Browser Exploitation Framework!

Cookbook Version Build Status



The following platforms and versions are tested and supported using Opscode's test-kitchen.
- Debian wheezy
- Debian jessie



Key Type Description
[beef][packages] Array Additional packages to install (default: [git, libsqlite3-dev, build-essential])
[beef][user] String BeEF user (default: beef)
[beef][group] String BeEF group (default: beef)
[beef][path] String BeEF installation path (default: /opt/beef)
[beef][git_repository] String BeEF repository url (default:
[beef][git_reference] String BeEF repository reference (default: beef-
[beef][ruby_bin_dir] String Ruby bin directory (default: /opt/chef/embedded/bin)


The [beef][config][beef] namespace is a Hash containing the BeEF configuration.

Default configuration is set from beef-


Use the [beef][service] attribute to override variables service configuration. See [default](attributes/service.rb) overrides.

All variables you can override can be found in [service template](templates/default/service/init.erb#L13-L20).



Just include beef in your node's run_list:

  "run_list": [


Just include beef::service in your node's run_list:

  "run_list": [
  "attributes": {
    "beef": {
      "service": {
        "NAME": "beef-xss"

Running tests

  • First, install dependencies:

    bundle install

  • Run Checkstyle and ChefSpec:

    bundle exec rake

  • Run Kitchen tests:

    bundle exec rake kitchen


  1. Fork the repository on Github
  2. Create a named feature branch (like add_component_x)
  3. Write your change
  4. Write tests for your change (if applicable)
  5. Run the tests, ensuring they all pass
  6. Submit a Pull Request using Github

License and Authors

Authors: Sliim

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Dependent cookbooks

This cookbook has no specified dependencies.

Contingent cookbooks

There are no cookbooks that are contingent upon this one.


This file is used to list changes made in each version of the BeEF cookbook.


  • New recipe: beef::service to install and enable BeEF service
  • Do not install ruby, use the ruby embedded with Chef by default
  • New attributes: [beef][ruby_bin_dir] and [beef][group]
  • Removed nohup process
Potential breaking changes
  • Reviewed configuration template and attributes
  • Set default attribute for BeEF (current)
  • Removed useless apt packages.


  • Chef 12 compatibility
  • Use Rake instead of Strainer
  • Test hardness (rubocop, chefspec, kitchen)
  • No cookbook dependencies


  • Attributes reorganization


  • Initial release of beef cookbook

Foodcritic Metric

0.3.0 passed this metric