-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added whenever gem for easily writing and deploying cron jobs #2706
Conversation
Generated by 🚫 Danger |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me
Awesome! @icarito ? |
Hi! |
I've added the cron daemon to our Docker definition - so the gem should work - but we still need to figure out when to run |
We can run the command whenever we redeploy or push to main branch on
server.
Can't we?
…On May 10, 2018 10:37 AM, "Sebastian Silva" ***@***.***> wrote:
I've added the cron daemon to our Docker definition - so the gem should
work - but we still need to figure out when to run whenever
--update-crontab.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<#2706 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ATwCYanitUw1FMpSGIH6ZHL2hbrdWu7Gks5tw8r7gaJpZM4T4ueE>
.
|
Yes! Thanks for clarifying when it needs to run.
…On 10/05/18 02:54, Naman Gupta wrote:
We can run the command whenever we redeploy or push to main branch on
server.
Can't we?
On May 10, 2018 10:37 AM, "Sebastian Silva" ***@***.***>
wrote:
> I've added the cron daemon to our Docker definition - so the gem should
> work - but we still need to figure out when to run whenever
> --update-crontab.
>
> —
> You are receiving this because your review was requested.
> Reply to this email directly, view it on GitHub
> <#2706 (comment)>,
> or mute the thread
>
<https://github.com/notifications/unsubscribe-auth/ATwCYanitUw1FMpSGIH6ZHL2hbrdWu7Gks5tw8r7gaJpZM4T4ueE>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2706 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAMMS63KtGOC-TNx45sOvJfW_v2HblxGks5tw_JKgaJpZM4T4ueE>.
|
Should we test this by pushing it to |
yes we can have a cron job that put timestamp in the text file. |
Should i add that example in this pr? I mean cron job. We will actually see this running once we implement reply by tweet and email digest. |
it's as you like; we could do a follow-up PR if you want to keep things
simple. Would you add it in the code or in the description on GitHub?
…On Thu, May 10, 2018 at 1:03 PM, Naman Gupta ***@***.***> wrote:
Should i add that example in this pr?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<#2706 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJ1UyqjP9fhjkvb3G2vhIeuU7DYXNks5txHLigaJpZM4T4ueE>
.
|
I will add a job into the config/schedule file using ruby code. |
After this we could also do testing for whenever using this gem https://github.com/rafaelsales/whenever-test |
Oh cool! Well, tell me if you want me to merge this or hold off a bit,
thank you!!!
…On Thu, May 10, 2018 at 1:12 PM, Naman Gupta ***@***.***> wrote:
After this we could also do testing for whenever using this gem
https://github.com/rafaelsales/whenever-test
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<#2706 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJ99ioeJycdZH5uFtu16EmTAwRtdbks5txHURgaJpZM4T4ueE>
.
|
I think we should merge this.. so that i can make a follow up pr for cron job discussed above based on this pr. Merging this pr won't affect anything as of now because there is currently no job. :) |
perfect!
…On Thu, May 10, 2018 at 1:28 PM, Naman Gupta ***@***.***> wrote:
I think we should merge this.. so that i can make a follow up pr for cron
job discussed above based on this pr. Merging this pr won't affect anything
as of now because there is currently no job. :)
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<#2706 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJ1U-aL2c_ssdTexHdLRP8Qo5YYuaks5txHjCgaJpZM4T4ueE>
.
|
…lab#2706) * Added whenever gem for easily writing and deploying cron jobs * Add cron for whenever gem
Added whenever gem for easily writing and deploying cron jobs
Sub-project part of Periodic Email Digests in #2104
rake test
fixes #0000
-style reference to original issue #@publiclab/reviewers
for help, in a comment belowIf tests do fail, click on the red
X
to learn why by reading the logs.Please be sure you've reviewed our contribution guidelines at https://publiclab.org/contributing-to-public-lab-software
We have a loose schedule of reviewing and pulling in changes every Tuesday and Friday, and publishing changes on Fridays.
Thanks!