I created this service to solve my own problems. Setting up system crons can get real annoying when you have multiple app servers.
Suggestion: Add a notify-on-failure attribute to cron jobs. If cron fails, notify via email or SMS.
Show HN: Cron.io - Sharing a by-product. Should this be a full service?
11–20 of 71 posts
Re: Show HN: Cron.io - Sharing a by-product. Should this be a full service?
#12I think I'd pay for the convenience and reliability, but I hope you'd have a small pricing option. I'd use <5 jobs at any one time, and probably wouldn't want to pay more than $3/month.
Re: Show HN: Cron.io - Sharing a by-product. Should this be a full service?
#13I've been using webcron.org for a few projects, works well enough, but my most important criteria is price for something this simple. It's really cheap, $0.00014 per request.
Re: Show HN: Cron.io - Sharing a by-product. Should this be a full service?
#14Love it.
I'm a big believer in choosing the right vocabulary. Half of the fogginess in communicating ideas comes from bad vocabulary, and matching that vocabulary to your user base.
For example, "signal" is a great word that describes the behavior. "Delegate" is also decent. "Dictionary" is not a good word. If you don't know that a dictionary is a key value store, it's not very obvious. Same with "hash"; unless you've been educated in data structures, a hash is either a mathematical function or a cannabis product.
Reason I bring it up: We don't manipulate "crons". We manipulate "jobs" in the crontab at /etc/crontab (short for cron table, I believe).
It's an exceptionally tiny nitpick of a really good idea. So keep up the good work and feel free to ignore my pedanticism.
Re: Show HN: Cron.io - Sharing a by-product. Should this be a full service?
#15Would creating 60 jobs polling the same URL at 1 min intervals translate to the site getting polled every second? Or is there batching/coalescing of the same-URL jobs?
Re: Show HN: Cron.io - Sharing a by-product. Should this be a full service?
#16Would creating 60 jobs polling the same URL at 1 min intervals translate to the site getting polled every second? Or is there batching/coalescing of the same-URL jobs?
The crons are spaced out over time.
This is actually why i took so long to launch the site. I've used the prototype version of this for a long time. The app is written in node so it is incredibly fast, like destroy the internet fast. That is why email confirmations are required and accounts are limited to 5 crons each. I will add a captcha on account confirmation shortly as well.
Re: Show HN: Cron.io - Sharing a by-product. Should this be a full service?
#17Very cool. And kudos on the clean documentation.
Re: Show HN: Cron.io - Sharing a by-product. Should this be a full service?
#18Would creating 60 jobs polling the same URL at 1 min intervals translate to the site getting polled every second? Or is there batching/coalescing of the same-URL jobs?
The crons are spaced out over time. This is actually why i took so long to launch the site. I've used the prototype version of this for a long time. The app is written in node so it is incredibly fast, like destroy the internet fast. That is why email confirmations are required and accounts are limited to 5 crons each. I will add a captcha on account confirmation shortly as well.
Do tell me you are checking robots.txt then. This has a great potential for DoS, email confirmations or not.
Re: Show HN: Cron.io - Sharing a by-product. Should this be a full service?
#19Since I'm doing something similar in an enterprise environment I suggest you to add , to each cron, a dates black-list. I mean a list of dates in which you do not want the job to be executed ( Christmas , Easter etc). Kudos for the clean documentation
Re: Show HN: Cron.io - Sharing a by-product. Should this be a full service?
#20Earlier quoted context omitted.
The crons are spaced out over time. This is actually why i took so long to launch the site. I've used the prototype version of this for a long time. The app is written in node so it is incredibly fast, like destroy the internet fast. That is why email confirmations are required and accounts are limited to 5 crons each. I will add a captcha on account confirmation shortly as well.
Do tell me you are checking robots.txt then. This has a great potential for DoS, email confirmations or not.
This is a prototype service and I am watching the activity closely.
I appreciate your concern.