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


btsync (5) Versions 0.1.26

Installs/Configures btsync

cookbook 'btsync', '= 0.1.26'
cookbook 'btsync', '= 0.1.26', :supermarket
knife cookbook site install btsync
knife cookbook site download btsync
Quality -%

btsync Cookbook

Fast, unlimited &amp secure file-syncing. Free from the cloud. Sync never stores your files on servers, so they stay safe from data breaches and prying eyes. A more detailed and in depth FAQ and documentation about bittorrent sync can be found on:

The btsync cookbook installs bittorrent sync and provides a simple LWRP for adding shared folders that are to be synced between multiple servers. When using a hosted chef install you will be able to use the search feature to automatically find and add additional nodes to bittorrent sync without making any modifications.


Please note btsync on linux requires glibc 2.3 or greater.


TODO: Full attributes will be completed soon.


<table> <tr> <th>Key</th> <th>Type</th> <th>Description</th> <th>Default</th> </tr> <tr> <td><tt>['btsync']['setup']['user']</tt></td> <td>String</td> <td>The user that the btsync daemon will run as</td> <td><tt>webserv</tt></td> </tr> <tr> <td><tt>['btsync']['setup']['bin_dir']</tt></td> <td>String</td> <td>Where the binary will be installed to (should be in your path)</td> <td><tt>/usr/local/bin/</tt></td> </tr> </table>



Just include btsync in your node's run_list:

  "run_list": [

Then add a path and options to your server role like so:

    "name": "examplerole",
    "chef_type": "role",
    "json_class": "Chef::Role",
    "description": "Example Role for BTSYNC",
    "override_attributes": {
                "user": "httpd",
                "group": "httpd"
                "storage_path": "/data/btsync",
                    "password": "SomeCoolPasswordForTheUI"
    "run_list": [


  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: Will Hattingh & contributors

Dependent cookbooks

partial_search >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

No quality metric results found