Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Scheduling remote Heroku workers with Resque-scheduler

branch: master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 .gitignore
Octocat-spinner-32 Gemfile
Octocat-spinner-32 Gemfile.lock
Octocat-spinner-32 LICENSE
Octocat-spinner-32 README.md
Octocat-spinner-32 Rakefile
Octocat-spinner-32 config.ru
Octocat-spinner-32 config_resque.rb
Octocat-spinner-32 resque_schedule.yml
README.md

UPDATE : This is quite obsolete since Cedar Stack on Heroku allows you to declare distinct task for each worker you start :

web:        bundle exec rails server -p $PORT
scheduler:  bundle exec rake resque:scheduler
worker:     bundle exec rake jobs:work

http://devcenter.heroku.com/articles/procfile


RemoteScheduler allows you to drive distant Heroku app workers, scheduling their tasks, using Resque Scheduler on Heroku.

Works on bambo-ree-1.8.7 and bamboo-mri-1.9.2

All you need is to schedule your tasks in resque_schedule.yml, to deploy and define these ENV vars (using heroku config ...) :

  • RESQUEWEB_LOGIN (to connect to the resque-web utility)

  • RESQUEWEB_PWD

  • REMOTE_REDIS_URL (the Redis To Go url of your main app)

Then, you're ok to run one (and only one) worker which will act as the scheduler for your distant main app.

I extracted this from the coming soon release of SubMate which needs very frequent tasks that Heroku's default cron can't handle.

Don't hesitate to contact me for any question or request !

Something went wrong with that request. Please try again.