Use job name as implicit class name in the schedule
When configuring the schedule, the only required argument is 'class'. On the other hand, the job name (hash key) is not too useful and usually just duplicates the resque worker class name (underscored). So instead of having to do: some_job: class: SomeJob cron: '* * * * *' another_job: class: AnotherJob every: 1m job_name_different_than_class: class: WeirdlyNamedClass You can now do: SomeJob: cron: '* * * * *' AnotherJob: every: 1m job_name_different_than_class: class: WeirdlyNamedClass By default, the job name will be treated as class name, but you can still provide a different job name and class name.
Fix "warning: already initialize constant Version"
…nitialized constant" warnings.
README: explain cron syntax and time zones.
…t's empty after the remove
add support for before_schedule and after_schedule hooks
remove puts from tests
Support ENV['BACKGROUND'] flag for daemonizing
This brings feature parity with the latest (HEAD) version of resque when running a daemonized worker (see: defunkt/resque@8d92f03).