The Resque wiki provide a sample cap task to manage Resque processes.

namespace :foreman do
  desc "Start the application services"
  task :start, :roles => :app do
    sudo "start #{application}"
  end

  desc "Stop the application services"
  task :stop, :roles => :app do
    sudo "stop #{application}"
  end

  desc "Restart the application services"
  task :restart, :roles => :app do
    run "sudo start #{application} || sudo restart #{application}"
  end

  desc "Display logs for a certain process - arg example: PROCESS=web-1"
  task :logs, :roles => :app do
    run "cd #{current_path}/log && cat #{ENV["PROCESS"]}.log"
  end

  desc "Export the Procfile to upstart scripts"
  task :export, :roles => :app do
    # 5 resque workers, 1 resque scheduler
    run "cd #{release_path} && rvmsudo bundle exec foreman export upstart /etc/init -a #{application} -u #{user} -l #{shared_path}/log  -f #{release_path}/Procfile.production -c worker=5,scheduler=1"
  end 
end

It builds off this blog post on managing and monitoring a Ruby application with Foreman and Upstart. That should point you in the right direction.

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:

• Install Redis on the droplet using this helpful article :
  [https://www.digitalocean.com/community/tutorials/how-to-install-and-use-redis](http:// “Link title”)

  • Use foreman/upstart as suggested in the comment above to detail the tasks/servers that you want to run. The procfile is what will be used to run the processes. The following links are helpful for understanding: [http://blog.daviddollar.org/2011/05/06/introducing-foreman.html](http:// “Link title”) [http://railscasts.com/episodes/281-foreman](http:// “Link title”)

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.