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

RSS

btsync (5) Versions 0.1.27

Installs/Configures btsync

Berkshelf/Librarian
Policyfile
Knife
cookbook 'btsync', '~> 0.1.27'
cookbook 'btsync', '~> 0.1.27', :supermarket
knife cookbook site install btsync
knife cookbook site download btsync
README
Dependencies
Quality 44%

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: http://www.bittorrent.com/sync

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.

Requirements

Please note btsync on linux requires glibc 2.3 or greater.

Attributes

TODO: Full attributes will be completed soon.

btsync::default

<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>

Usage

btsync::default

Just include btsync in your node's run_list:

{
  "name":"my_node",
  "run_list": [
    "recipe[btsync::default]"
  ]
}

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": {
        "btsync":{
            "setup":{
                "user": "httpd",
                "group": "httpd"
            },
            "main_options":{
                "storage_path": "/data/btsync",
                "webui":{
                    "password": "SomeCoolPasswordForTheUI"
                }
            },
            "shared_folders":{
                "DescriptiveNameForPathToSearchON":{
                    "dir":"/path/to/some/directory/",
                    "secret":"S0M3L0NGB7SYNCG3N3R4T3DS3CR37",
                    "SyncIgnore":[".DS_Store",".DS_Store?","._*",".Spotlight-V100",".Trashes","Icon?","ehthumbs.db","desktop.ini","Thumbs.db","somefile.log","logs/*"]
                 },
                "AnotherDirectoryToSync":{
                  "dir":"/path/to/some/other/directory/",
                  "secret":"S0M3L0NGB7SYNCG3N3R4T3DS3CR372",
                  "SyncIgnore":[".DS_Store",".DS_Store?","._*",".Spotlight-V100",".Trashes","Icon?","ehthumbs.db","desktop.ini","Thumbs.db","somefile.log"]
                }
               }
            }
        }
    },
    "run_list": [
        "recipe[btsync::default]"
    ]
}

Contributing

  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 https://github.com/Nitecon/btsync/graphs/contributors

Dependent cookbooks

partial_search >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Collaborator Number Metric
            

0.1.27 failed this metric

Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric
            

0.1.27 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a CONTRIBUTING.md file

Foodcritic Metric
            

0.1.27 failed this metric

FC034: Unused template variables: btsync/templates/default/btsync-options.json.erb:1
FC064: Ensure issues_url is set in metadata: btsync/metadata.rb:1
FC065: Ensure source_url is set in metadata: btsync/metadata.rb:1
FC066: Ensure chef_version is set in metadata: btsync/metadata.rb:1
FC069: Ensure standardized license defined in metadata: btsync/metadata.rb:1
FC072: Metadata should not contain "attribute" keyword: btsync/metadata.rb:1
Run with Foodcritic Version 12.2.1 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

License Metric
            

0.1.27 passed this metric

No Binaries Metric
            

0.1.27 passed this metric

Publish Metric
            

0.1.27 passed this metric

Supported Platforms Metric
            

0.1.27 passed this metric

Testing File Metric
            

0.1.27 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a TESTING.md file

Version Tag Metric
            

0.1.27 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must include a tag that matches this cookbook version number