Source: ruby-sidekiq
Section: ruby
Priority: optional
Maintainer: Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>
Uploaders: Pirate Praveen <praveen@debian.org>
Build-Depends: debhelper (>= 11~),
               gem2deb,
               libjs-d3,
               libjs-jquery,
               libjs-jquery-timeago,
               libjs-rickshaw,
               libjs-bootstrap,
               procps,
               redis-server,
               ruby-actionmailer,
               ruby-activerecord,
               ruby-celluloid (>= 0.16.0),
               ruby-concurrent,
               ruby-connection-pool (<< 3.0),
               ruby-connection-pool (>= 2.2.2~),
               ruby-coveralls,
               ruby-railties,
               ruby-redis (>= 3.3.5~),
               ruby-redis-namespace (<< 2.0),
               ruby-redis-namespace (>= 1.5.2),
               ruby-rack-protection (>= 1.5.0),
               ruby-sinatra,
               ruby-tilt (>= 2.0.1)
Standards-Version: 4.2.1
Vcs-Git: https://salsa.debian.org/ruby-team/ruby-sidekiq.git
Vcs-Browser: https://salsa.debian.org/ruby-team/ruby-sidekiq
Homepage: http://sidekiq.org
Testsuite: autopkgtest-pkg-ruby
XS-Ruby-Versions: all

Package: ruby-sidekiq
Architecture: all
XB-Ruby-Versions: ${ruby:Versions}
Depends: libjs-bootstrap,
         ruby | ruby-interpreter,
         ruby-celluloid (>= 0.16.0),
         ruby-concurrent,
         ruby-connection-pool (<< 3.0),
         ruby-connection-pool (>= 2.2.2~),
         ruby-json,
         ruby-redis (>= 3.3.5~),
         ruby-redis-namespace (<< 2.0),
         ruby-redis-namespace (>= 1.5.2),
         ruby-rack-protection (>= 1.5.0),
         ${misc:Depends},
         ${shlibs:Depends}
Description: Simple, efficient background processing for Ruby
 Sidekiq uses threads to handle many jobs at the same time in the
 same process.  It does not require Rails but will integrate tightly with
 Rails 3/4 to make background processing dead simple.
 .
 Sidekiq is compatible with Resque.  It uses the exact same
 message format as Resque so it can integrate into an existing Resque
 processing farm.
 .
 You can have Sidekiq and Resque run side-by-side at the same time and
 use the Resque client to enqueue jobs in Redis to be processed by Sidekiq.