Thanks for pointing me in the right direction. There were still a few issues that I faced in implementing this properly, so I thought I’d help others trying to implement this in their app. I assume that resque has already been implemented in the app locally. I followed these steps for implementing resque on my app hosted on digital ocean:
This is what my Procfile looks like :
worker: RAILS_ENV=production bundle exec rake resque:work QUEUE='*'
scheduler: RAILS_ENV=production bundle exec rake resque:scheduler
faye: bundle exec rackup private_pub.ru -s thin -E production
- Make changes in the resque configuration to run the resque server on the app’s production IP:
in initializers/resque-web.rb
Resque.redis = ENV['REDIS_URL']
Resque.after_fork = Proc.new { ActiveRecord::Base.establish_connection }
- The following capistrano tasks need to be created to run the servers/tasks mentioned in the Procfile :
in config/deploy.rb
task :export do
on roles(:app) do
execute [
"cd #{release_path} &&",
'export rvmsudo_secure_path=0 && ',
"#{fetch(:rvm_path)}/bin/rvm #{fetch(:rvm_ruby_version)} do",
'rvmsudo',
'RAILS_ENV=production bundle exec foreman export --app appname --user username -l logfile-path -f ./Procfile upstart /etc/init -c worker=1,scheduler=1,faye=1'
].join(' ')
end
end
task :restart do
on roles(:app) do
execute :sudo, "restart appname"
end
end
after :publishing, :export
after :publishing, :restart
This should get the workers going.

by Etel Sverdlov
This tutorial covers the Redis Installation, some simple Redis operations, and the 5 Redis data types. Redis, developed in 2009, is a flexible, open-source, key value data store that allows users to store vast amounts of data without the limits of a relational database.