Show HN: Cron.io - Sharing a by-product. Should this be a full service?
1–10 of 71 posts
Re: Show HN: Cron.io - Sharing a by-product. Should this be a full service?
#2I created this service to solve my own problems. Setting up system crons can get real annoying when you have multiple app servers.
Re: Show HN: Cron.io - Sharing a by-product. Should this be a full service?
#3I would pay for this provided it was reliable and relatively cheap. $1/cron, for e.g.
Re: Show HN: Cron.io - Sharing a by-product. Should this be a full service?
#4Yes! I currently have a server ran specifically for managing my cron tasks, I would love to outsource it to a reliable company. If you could guarantee reliability then I'd love to use it. Not sure about pricing though, but I'm paying $20/m for the server I rent (Linode) so if you could guarantee reliability and it meant I didn't have to manage anything myself I'd be happy to pay around that or more.
Re: Show HN: Cron.io - Sharing a by-product. Should this be a full service?
#5This seems great! The requests are a bit lengthy but I'm sure they could be simplified further later on.
Likely bug: I just signed up and clicked the activation link and it said that my account was already confirmed.
Re: Show HN: Cron.io - Sharing a by-product. Should this be a full service?
#6This seems great! The requests are a bit lengthy but I'm sure they could be simplified further later on. Likely bug: I just signed up and clicked the activation link and it said that my account was already confirmed.
In practice hopefully you would never have to use curl with the full service. I want to make an npm command line app to make things from the command line simple. Other use cases are libraries for different languages to integrate into your application.
I'd say you accidentally clicked the link twice, or maybe your browser made two requests.
Re: Show HN: Cron.io - Sharing a by-product. Should this be a full service?
#7Having created dozens of cron jobs across several apps(as I'm sure half of us here have), thank you.
Re: Show HN: Cron.io - Sharing a by-product. Should this be a full service?
#8Definitely a good idea! The only thing that would make me hesitant to use this service is that you are at the mercy of any kind of network outages between your servers and mine. If I have a DNS outage, a main network node down on the route when the request is made, etc then my cron will not get executed. A super great feature would be the ability to specify a retry flag for individual jobs. So if you attempt to call a cron endpoint on my server unsuccessfully, your service would keep trying every couple minutes until successful (or the next scheduled execution occurs). Otherwise, good work and good luck - surely solves a pain point many cloud devs have!
Re: Show HN: Cron.io - Sharing a by-product. Should this be a full service?
#9I would pay for this provided it was reliable and relatively cheap. $1/cron, for e.g.
I would pay $0.10 per X cron requests (a la AWS pricing). $1/cron? Above $10-20/month, I'd just write it myself.
Re: Show HN: Cron.io - Sharing a by-product. Should this be a full service?
#10This would be an excellent service for preventing Heroku apps from falling asleep >:-)
Joking aside, great idea. This is useful.