which toll should i use? my task needs to be run after 1 hour or other
time
unit afte r the record has been created.
thx
tom
which toll should i use? my task needs to be run after 1 hour or other
time
unit afte r the record has been created.
thx
tom
Most popular gem:
[GitHub - sidekiq/sidekiq: Simple, efficient background processing for Ruby](https://link.nylas.com/
link/2s7ds13v0mefx2ttu8i2zt1di/local-
a52b4ec6-3348/0?redirect=https%3A%2F%2Fgithub.com%2Fmperham%2Fsidekiq)
-----
Przemek Kosakowski
On maj 26 2016, at 4:37 pm, tom <[email protected]> wrote:
which toll should i use? my task needs to be run after 1 hour or other time
unit afte r the record has been created.
thx
tom
--
You received this message because you are subscribed to the Google
Groups
“Ruby on Rails: Talk” group.
To unsubscribe from this group and stop receiving emails from it, send
an
email to
[[email protected]](mailto:rubyonrails-
[email protected]).
To post to this group, send email to rubyonrails-
[email protected].
To view this discussion on the web visit
[https://groups.google.com/d/msgid
/rubyonrails-talk/CADQqhMdDB7TwOOnHk_zuuGHCdAWeaZrkRpz%3DH%2BsS4U6XnYCY%3Dw%40
mail.gmail.com](https://groups.google.com/d/msgid/rubyonrails-talk/CADQqhMdDB7
TwOOnHk_zuuGHCdAWeaZrkRpz%3DH%2BsS4U6XnYCY%3Dw%40mail.gmail.com?utm_medium=ema
il&utm_source=footer).
For more options, visit https://groups.google.com/d/optout.
Checkout both https://github.com/tomykaira/clockwork
and GitHub - sidekiq/sidekiq: Simple, efficient background processing for Ruby
I have used both of them for scheduling different kind of background
jobs.
Saurav
I second this. Sidekiq (especially version 4) is amazing. Clockwork is
great too for scheduling recurring jobs. There was a sidetiq which
would schedule sidekiq jobs however it is not actively being developed
and lacks sidekiq 3.5.1 and 4.0 support. You have to use a version
that’s back ported with Celluloid 0.17.1 (I think that’s the version
number). I’d stay away from sidetiq and focus on clockwork and sidekiq
itself.
If sidekiq becomes too much technical debt and you need something that
just works and is easy to use minus the reds dependency and monitoring
with bluepill or god, I recommend sucker_punch
https://github.com/brandonhilkert/sucker_punch. It does not have job
re-enqueing or persistence past the memory space (if you restart your
app server (puma/passenger/unicorn) you lose your pending jobs. But
it’s a great little gem and I use it for lots of small projects where
sidekiq is overkill.
Cheers,
James
Subscribe to my Youtube Channel: https://www.youtube.com/shakycode
https://www.youtube.com/c/shakycode
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
Sponsor our Newsletter | Privacy Policy | Terms of Service | Remote Ruby Jobs