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


geminabox (4) Versions 0.1.1

Installs and configures Geminabox

cookbook 'geminabox', '= 0.1.1'
cookbook 'geminabox', '= 0.1.1', :supermarket
knife cookbook site install geminabox
knife cookbook site download geminabox
== Geminabox On Chef Configures and installs {geminabox}[] via Chef to provide a private (and optionally secured) gem store. == Features * Optional SSL * Optional user/pass authentication == Requirements Currently this cookbook uses a defined set of applications with the intention to expand coverage of other options (like passenger, thin, apache, monit, etc). At present, these are supported: * Nginx * Unicorn * Bluepill == Suggested additions It is highly suggested to include the BagConfig cookbook for storing sensitive configuration values within encrypted data bag entries: == What you get By default, this cookbook will provide a Geminabox instance available via http://node_address. It uses a unicorn + nginx pairing with bluepill monitoring the unicorn processes. It also comes with an upstart configuration. == Adding extras === SSL To enable SSL, provide a key and cert pair: node[:geminabox][:ssl] = {:key => '/path/to/ssl.key', :cert => '/path/to/ssl.cert', :enabled => true} You can also provide the the actual key and cert pair in the attributes (though if this approach is used, it is advised to use the BagConfig cookbook and encrypt the data bag entry). === Authentication To enable authentication, provide a path to the htpasswd file to use or the raw contents of the htpasswd file: node[:geminabox][:auth_required] = '/path/to/htpasswd.file' or, you can provide a hash of user/password pairs and have the auth file dynamically created: node[:geminabox][:auth_required] = {'user1', 'secret'} Again, with providing plaintext passwords, it is suggested to use the BagConfig cookbook and encrypt the configuration data bag entry. Finally, the password file can be provided via data bag. There are two ways the data bag can be formatted. First is providing the content of an htpasswd generated file. The second is to provide username/password pairs in the data bag. == Issues Please report any bugs to the {issues}[] section on the github repo. If you have fixes, updates or new features, please fork and send a pull request == Thanks Many thanks to {Tom Lea}[] for {Geminabox}[] == License MIT License (see LICENSE)

Dependent cookbooks

nginx >= 0.0.0
bluepill >= 0.0.0
unicorn >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

No quality metric results found