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

RSS

sidekiq (9) Versions 4.0.3

Installs/Configures sidekiq

Policyfile
Berkshelf
Knife
cookbook 'sidekiq', '~> 4.0.3', :supermarket
cookbook 'sidekiq', '~> 4.0.3'
knife supermarket install sidekiq
knife supermarket download sidekiq
README
Dependencies
Quality 17%

Sidekiq

Description

Requirements

Attributes

Usage

sidekiq "my-queue" do
  user "deploy"
  concurrency 2
  processes 2
  queues "job-queue" => 5, "other-queue" => 1
end

Sidekiq Monitor

There are two ways to deploy a Sidekiq Monitor. You can run the sidekiq::monitor
recipe, which will install a service named sidekiq-monitor configured based on
node attributes. You can also use the sidekiq_monitor LWRP.

Both ways use a small wrapper Rack application to run the monitoring
Sinatra app that ships with Sidekiq.

sidekiq::monitor recipe

The user by which Sidekiq Monitor is run is set via the node attribute
node['sidekiq']['monitor']['user'].

The RACK_ENV by which Sidekiq Monitor is run is set via
node['sidekiq']['monitor']['rack_env'].

Ruby should be in the PATH. This can by set by adding to the array
node['sidekiq']['monitor']['path_additions'].

sidekiq_monitor LWRP

The LWRP can be used where multiple Sidekiq Monitors may be on the same
node.

service 'my-sidekiq-monitor' do
  supports :enable => true, :disable => true, :restart => true, :reload => true
  action :nothing
end

sidekiq_monitor 'my-sidekiq-monitor' do
  user 'myuser'
  group 'staff'
  path_additions ['/opt/rbenv/versions/2.0.0/bin']

  redis_host node['privateaddress']
  redis_port 6379
  redis_db 11
  redis_namespace 'sk'

  unicorn_host node['privateaddress']
  unicorn_port 8880
  rack_env 'production'

  notifies :restart, 'service[my-sidekiq-monitor]'
end

By default the LWRP will create a user 'sidekiq-monitor' and group
'sidekiq-monitor' to run as. It will check out a small Rack application
at /opt/sidekiq-monitor. Configuration files will go into
/etc/sidekiq-monitor and log files will go in
/var/log/sidekiq-monitor.

Dependent cookbooks

smf >= 2.1.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Collaborator Number Metric
            

4.0.3 failed this metric

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

Contributing File Metric
            

4.0.3 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
            

4.0.3 failed this metric

FC064: Ensure issues_url is set in metadata: sidekiq/metadata.rb:1
FC065: Ensure source_url is set in metadata: sidekiq/metadata.rb:1
FC066: Ensure chef_version is set in metadata: sidekiq/metadata.rb:1
FC069: Ensure standardized license defined in metadata: sidekiq/metadata.rb:1
FC085: Resource using new_resource.updated_by_last_action to converge resource: sidekiq/providers/default.rb:21
FC085: Resource using new_resource.updated_by_last_action to converge resource: sidekiq/providers/default.rb:130
FC085: Resource using new_resource.updated_by_last_action to converge resource: sidekiq/providers/monitor.rb:2
FC085: Resource using new_resource.updated_by_last_action to converge resource: sidekiq/providers/monitor.rb:125
Run with Foodcritic Version 16.3.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

No Binaries Metric
            

4.0.3 passed this metric

Testing File Metric
            

4.0.3 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
            

4.0.3 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