This repository was archived by the owner on Dec 3, 2019. It is now read-only.
Repository navigation
This repository was archived by the owner on Dec 3, 2019. It is now read-only.
Add the whenever gem for cron jobs #163
Description
Feature
Why is this feature being added?
We need to be able to have recurring cron jobs ran, on our behalf. For example, to hit GitHub's API, or the Meetup API, on a daily basis, to pull in current statistics or Meetup events.
The whenever gem is a perfect tool to solve this.
This issue will complete the implementation for #153
What should your feature do?
- Install the whenever gem
- Write a shell script for it
- Update the Dockerfile to call the script instead of the current CMD
Activity
hpjaj commentedon Sep 22, 2017
@rickr - ping
hpjaj commentedon Oct 10, 2017
@ohaiwalt - curious if this issue is something you’re able to do?
I can take care of installing the
whenevergem. Would need your assistance on the second two bullet points.hollomancer commentedon Oct 13, 2017
@hpjaj, would this implementation accomplish what you need?
http://derekbarber.ca/blog/2015/09/10/scheduling-background-jobs-in-rails-using-sidekiq/
hpjaj commentedon Oct 13, 2017
@hollomancer - Nice find. The only issue is deploying the setup to the server. It "seems" like we would need to do similar config, as what we would need for just using the Whenever gem by itself.
But I don't know. That would be a question for @rickr or @ohaiwalt ?
Whichever approach is easier for them to setup, I can take care of the rest.
hollomancer commentedon Oct 13, 2017
I think that in this case, it would just be happening in the same pod as operationcode_backend, wouldn't it? That would skip items 2 and 3.
hpjaj commentedon Oct 13, 2017
¯_(ツ)_/¯
The part of the article I am unsure on is the Deploying Your Background Jobs, since we do not use capistrano.
Are you thinking that we can just setup a
config/deploy.rbfile as they describe, merge to master and deploy, and it would just work?If yes, then yes, this would be a great option.
hollomancer commentedon Oct 13, 2017
I'm not familiar with Capistrano - but yeah, I would think we would call
whenever --update-crontabsomewhere like .travis.yml or bin/deployhpjaj commentedon Oct 13, 2017
Yeah, that is the missing link for me, too. @ohaiwalt ?
hollomancer commentedon Oct 13, 2017
Let's go ahead and get what we need in terms of cronjobs specified - we can worry about the deployment piece afterwards.
BRIMIL01 commentedon Oct 1, 2018
Since the project already uses sidekiq would it be better to use something like https://github.com/moove-it/sidekiq-scheduler?
robbkidd commentedon Oct 1, 2018
I agree with using more Sidekiq. I've had recent good experience with sidekiq-cron and recommend it.
BRIMIL01 commentedon Oct 3, 2018
I can take this and add https://github.com/ondrejbartas/sidekiq-cron support if that is aligned with how we want to manage jobs in backend.
apex-omontgomery commentedon Oct 6, 2018
Assigning myself as placeholder for you. :)