Closed rvanrinsum closed 9 months ago
actually, also before that uninitialized constant error, this is printed:
$ bundle exec clock
Because this is not a rails application, we do not know how to load your
rake tasks. You can do this yourself at the top of your Clockfile if you want
to run rake tasks from ruby-clock.
bundler: failed to load command: clock (/Users/xxxx/.asdf/installs/ruby/3.1.2/bin/clock)
Which is weird bc I'm in a Rails project dir
removing using RubyClock::DSL
and using schedule.every ...
fixed it. prob has to do with the different gem version
Hi @rvanrinsum
First of all sorry for the delayed response, I need to tweak my github notification preferences.
Glad you found a workaround. Not sure if you noticed the note at the top of the readme, which says the readme is for 2.0 beta. I should probably make that more visible, or maybe keep the beta stuff in another branch. sorry about that!
The good news is that since you wrote, the beta has improved quite a bit. you can use this in your gemfile
gem 'ruby-clock', tag: 'v2.0.0.beta9'
And everything in the readme here should work: https://github.com/jjb/ruby-clock
Or, if that doesn't work for you, you can use 1.0.0, and these instructions: https://github.com/jjb/ruby-clock/tree/v1.0.0
If you are currently on 1.0.0, look at the upgrade notes here: https://github.com/jjb/ruby-clock/blob/main/CHANGELOG.md
let me know if you have any problems!
Hey man, this is exactly what I need, but I can't get it to work.
on
bundle exec clock
I get:Tried a few things but no luck, any idea why this doesn't work out of the box? The binstub that it generated is this: