clockwork
clockwork copied to clipboard
A scheduler process to replace cron.
Current style has long been to use Minitest instead of MiniTest, and with minitest 5.19, MiniTest usage support is hidden unless explicitly setting ENV["MT_COMPAT"]. https://github.com/minitest/minitest/commit/a2c6c18570f6f0a1bf6af70fe3b6d9599a13fdd6 Use Minitest instead of MiniTest...
As of clockwork git head ( https://github.com/Rykian/clockwork/commit/7ed9042e49cd841e41fe516f74ffd290fcb2105f ), testsuite fails with Minitest 5.20 as: ``` $ ruby -Ilib:test -rclockwork -e "Dir.glob('./test/**/*_test.rb').sort.each {|t| require t}" Loaded suite -e Started 1) Error:...
We noticed this issue when we had every(1.day) and :at a specific timeframe. We used this as a workaround to ensure that we do not miss invocations of a job....
I have been using the following cron: `every(1.week, 'create_week.job', :at => 'Monday 00:05', :tz => 'UTC')` It's not getting triggered. I also have `every(30.minutes, 'coins.count.job')` that is working completely fine....
I read through the docs, it seems conflict between `at:` and `thread:` - `at:` **If another task is already running at the specified time, clockwork will skip execution of the...
The idea is to support wildcards when setting a day of week. A use case for this is if you want to send an alert every hour only on weekdays....
Excellent library! Two related services that could be worth mentioning in the README. 1. GoodJob (https://github.com/bensheldon/good_job), a modern asynchrony job worker. 2. Consul (https://github.com/hashicorp/consul), a service discovery and mesh tool,...
I used `module_eval` to make a `clock.rb` file easier to read, given a particular use-case.
the readme says: > If another task is already running at the specified time, clockwork will skip execution of the task with the :at option. If this is a problem,...
https://github.com/thuehlinger/daemons https://rubygems.org/gems/daemons/