Guard::Resque automatically starts/stops/restarts resque scheduler
forked from Guard::Resque
Please be sure to have Guard installed before continue.
Install the gem:
gem install guard-resque-scheduler
Add it to your Gemfile (inside test group):
gem 'guard-resque-scheduler'
Add guard definition to your Guardfile by running this command:
guard init resque-scheduler
Please read Guard usage doc.
guard 'resque-scheduler', :environment => 'development' do
watch('config/schedule.yml')
end
Scheduler only needs to reload when the schedule changes, so point it there.
You can customize the resque task via the following options:
environment
: the rails environment to run the workers in (defaults tonil
)task
: the name of the rake task to use (defaults to"resque:scheduler"
)verbose
: whether to use verbose logging (defaults tonil
)trace
: whether to include--trace
on the rake command (defaults tonil
)stop_signal
: how to kill the process when restarting (defaults toQUIT
)
- Source hosted at GitHub
- Report issues/Questions/Feature requests on GitHub Issues
Pull requests are very welcome! Make sure your patches are well tested. Please create a topic branch for every separate change you make.
gem install guard-resque-scheduler-0.x.x.gem
-
Update the version number in
lib/guard/resque-scheduler/version.rb
-
Update
CHANGELOG.md
-
Build the gem:
gem build guard-resque-scheduler.gemspec
-
Push to rubygems.org:
gem push guard-resque-scheduler-0.x.x.gem
Ideas for this gem came from Guard::WEBrick.
I hacked this together from the guard-delayed
gem for use with Resque. All credit go to the original authors though. I just search/replaced and tweaked a few things
Hacked up Guard::Resque because I needed a simple way to launch the scheduler daemon. Mostly a search/replace, and I removed some of the resque options that didn't apply.