21–30 of 30 posts
I love all the options we have today. At Cronitor we are seeing a lot of users migrating to Airflow, Kubernetes cron jobs, and scheduled lambdas. Like databases, different workloads will benefit from different guarantees. Look for the right tool for the job, not the right tool for all time.
Is there a reason not to consider apache airflow? https://airflow.apache.org/ You could run it on a digital ocean droplet so you don't have to worry about your laptop turning off. It covers retry and cron-style job kickoffs.
You can create systemd timers and services quite easily with NixOS configuration : https://nixos.wiki/wiki/Nix_Cookbook
Jenkins works reasonably well as a job scheduler. The UI is functional if not pretty, it is fairly easy to configure and use even for a large number of jobs, and the plugin ecosystem allows you to extend it in many ways without writing any code.
I don't get the systemd hate in this specific case. Their timers are pretty much the best possible option you have to schedule jobs, hands down. No cron Daemon is ever going to get there due to the lack of deep integration with the rest of the init system. I know it takes a while to get used to the ini file madness, but honestly, I can't detect so much boilerplate there: every single line in my units and timers makes…
As a result, I can execute it include it in another ansible role, or use bigsudo to apply it as a one-off command:
bigsudo yourlabs.timer @somehost name=your-backup cmd=/your/backup.sh oncalendar='*-*-* 00:00:00 Europe/Paris'I don't get the systemd hate in this specific case. Their timers are pretty much the best possible option you have to schedule jobs, hands down. No cron Daemon is ever going to get there due to the lack of deep integration with the rest of the init system. I know it takes a while to get used to the ini file madness, but honestly, I can't detect so much boilerplate there: every single line in my units and timers makes…
Also `systemctl edit` is a thing. No need to fiddle with 'what directory is this thing in?'
Earlier quoted context omitted.
Also `systemctl edit` is a thing. No need to fiddle with 'what directory is this thing in?'
Yeah with the --full option you can be sure you've got your own full copy to work with in /etc