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


omnibus-gitlab (10) Versions 0.1.4

Installs/Configures GitLab using omnibus-gitlab

cookbook 'omnibus-gitlab', '= 0.1.4'
cookbook 'omnibus-gitlab', '= 0.1.4', :supermarket
knife supermarket install omnibus-gitlab
knife supermarket download omnibus-gitlab
Quality 0%


TODO: Enter the cookbook description here.

Supported Platforms

TODO: List your supported platforms.


<table> <tr> <th>Key</th> <th>Type</th> <th>Description</th> <th>Default</th> </tr> <tr> <td><tt>['cookbook-omnibus-gitlab']['bacon']</tt></td> <td>Boolean</td> <td>whether to include bacon</td> <td><tt>true</tt></td> </tr> </table>



Include cookbook-omnibus-gitlab in your node's run_list:

  "run_list": [


  1. Fork the repository on Github
  2. Create a named feature branch (i.e. add-new-recipe)
  3. Write you change
  4. Write tests for your change (if applicable)
  5. Run the tests, ensuring they all pass
  6. Submit a Pull Request

License and Authors


Dependent cookbooks

This cookbook has no specified dependencies.

Contingent cookbooks

There are no cookbooks that are contingent upon this one.


Create the SSL key and certificate for GitLab CI

Also render ci_external_url and git_data_dir in gitlab.rb


Prevent storing secrets in the Chef node object

Cookbook-omnibus-gitlab allows you to keep secret Omnibus-gitLab settings (passwords, keys) in an encrypted data bag. These secrets then get decrypted during the Chef client run on your GitLab server. Due to a programming error, the cookbook-omnibus-gitlab would then send the plaintext secrets back to the Chef server to be stored in the node's database record. This defeats one of the purposes of using encrypted data bags, namely to keep plaintext secrets off of the Chef server.

In version 0.1.2 we make sure that the secrets stored in the encrypted data bag do not get sent back to the server.

If you have been using cookbook-omnibus-gitlab with an encrypted data bag you should upgrade to cookbook-omnibus-gitlab 0.1.2 or newer and inspect your GitLab nodes to look for secrets:

knife node show --format json

If some of your cookbook-omnibus-gitlab secrets got uploaded to the Chef server you can delete them from the node object using knife node edit after you upgrade cookbook-omnibus-gitlab to 0.1.2 or newer.

As an additional measure you may want to consider changing the affected passwords and keys.



Initial release of cookbook-omnibus-gitlab

Foodcritic Metric

0.1.4 failed this metric

FC003: Check whether you are running with chef server before using server-specific features: /tmp/cook/b11be63968a8d170d05f3b8b/omnibus-gitlab/recipes/default.rb:15