Padrino + Sidekiq = ♥

boot.rb

# config/boot.rb

# ...
# Load our dependencies
require 'rubygems' unless defined?(Gem)
require 'bundler/setup'
Bundler.require(:default, PADRINO_ENV)

# Load worker definitions
require File.join(PADRINO_ROOT, 'config', 'workers.rb')

# ...

Gemfile

# ...
gem 'sidekiq'
# ...

hard_worker.rb

# workers/hard_worker.rb

class HardWorker
  include Sidekiq::Worker

  def perform(name, count)
    puts 'Doing hard work'
  end
end

Procfile

web: bundle exec thin start -p $PORT
worker: bundle exec sidekiq -r ./config/workers.rb

test.rb

# app/controllers/test.rb

YourApp.controller do
  get '/test' do
    HardWorker.perform_async('bob', 5)
  end
end

workers.rb

# config/workers.rb

Dir[File.expand_path('../../workers/*.rb', __FILE__)].each{|file|require file}

@jeregrine in config/workers.rb :

require File.expand_path('../boot.rb', __FILE__)

This way all your workers can do anything that you could do in a padrino console like access models.

@kke wouldn't your config/workers be loading up the boot and the boot loading up the workers?

In case anyone is trying to to get the sidekiq web interface running, just add the following to config.ru

# Load sidekiq web interface
require 'sidekiq/web' 
map('/sidekiq') { run Sidekiq::Web }

require File.expand_path("../config/boot.rb", __FILE__)
run Padrino.application