4 ms·
I don't get it. What's so hard about cron jobs that you have to write a wrapper for it? It is easy to understand if you just read the crontab file comment at th
by Walkman 12y ago
I don't get it. What's so hard about cron jobs that you have to write a wrapper for it? It is easy to understand if you just read the crontab file comment at the top.
There is just two commands:
crontab -l
for listing
crontab -e
for editing. What else do you need?
With this, instead of learning crontab simple syntax, you need to:
- install this package
- learn its API
- run it and still edit the crontab file :D
seems like not worth it.
- ddv_ 12y agoWhenever gem does the same thing. So you can keep it under version control with your project.
- icebraining 12y agoIt's just a text file, why not just add it to the version control of your project? If it's because users can only have a single crontab, you can always use system crontabs instead or "cat" them together.
- Walkman 12y agoYou can install a new crontab file with $ crontab [ -u user ] file
- est 12y agoHow about dynamic periodic tasks? For instance, server side exponential backoff.
- noselasd 12y agoThis approach has a human in the loop. There's plenty of use cases where you want a program to edit cron jobs.