Update config.yml
clean up namespacing code
Refactor signal handling to use a pipe

This commit removes the need to poll a global array for received signals every
second by introducing an internal pipe(2).

The writing end of the pipe is being used in the block trapping the signals.
Whenever a signal is received, the signal's name gets written to the pipe.

Instead of polling for received signals, the code now uses select(2) to
check whether the internal pipe has been written to and can be read from.
select(2) is blocking until one of the passed file descriptors is ready for
reading/writing or has an exception, which means the code does not need to use
`sleep 1` anymore.

So when a signal is sent to the sidekiq process, the signal name gets written to
the internal pipe, select(2) returns and the process can react according to the
received signal. After handling a signal, select(2) gets called again and blocks
until receiving another signal.
Do not use globals for signal handling

This moves the trapping and handling of signals into `Sidekiq::CLI#run`,
so no more global self-pipe is necessary.
Remove unused instance variables

These two lines are not needed anymore after fb2c2865.
Added support for many Sidekiq instances on the upstart script.
Merge pull request #761 from mrnugget/signal_handling

Refactor signal handling to use a pipe
Merge pull request #763 from dariocravero/upstart-support-many

Added support for many Sidekiq instances on the upstart script.
Adding moar badges
Merge pull request #765 from krainboltgreene/patch-1

Adding moar badges
remove this annoyance
Added a comment why REDISTOGO_URL is supported
Merge pull request #767 from keithpitt/patch-2

Added a comment why REDISTOGO_URL is supported
Adding coveralls support
Adding coveralls as a development dependency
fix pagination when @total_size is devisible by @count
Merge pull request #774 from pitr/fix_pagination

fix pagination when @total_size is devisible by @count
Update README.md

Add screenshot, always be selling!
Call 'exhausted' worker method after retries

When the maximum number of retries is hit and the message is about
to be thrown away, give the option of allowing the worker to say
goodbye by defining an 'exhausted' method on the worker.
Remedied requirement to bring your own table to the flipping method

See https://twitter.com/mperham/status/314141110513586177