cheek alternatives and similar packages
Based on the "Job Scheduler" category.
Alternatively, view cheek alternatives based on common mentions on social networks and blogs.
8.3 7.7 cheek VS gocronEasy and fluent Go cron scheduling. This is a fork from https://github.com/jasonlvhit/gocron
4.0 10.0 cheek VS DaguA No-code workflow executor with built-in web UI [Moved to: https://github.com/yohamta/dagu]
Do you think we are missing an alternative of cheek or a related project?
cheek, of course, stands for
Execution of tas
cheek is a KISS approach to crontab-like job scheduling. It was born out of a (/my?) frustration about the big gap between a lightweight crontab and full-fledged solutions like Airflow.
cheek aims to be a KISS approach to job scheduling. Focus is on the KISS approach not to necessarily do this in the most robust way possible.
Fetch the latest version for your system below.
You can (for example) fetch it like below, make it executable and run it. Optionally put the
cheek on your
curl https://storage.googleapis.com/better-unified/darwin/amd64/cheek -o cheek chmod +x cheek ./cheek
Create a schedule specification using the below YAML structure:
tz_location: Europe/Brussels jobs: foo: command: date cron: "* * * * *" on_success: trigger_job: - bar bar: command: - echo - bar - foo coffee: command: this fails cron: "* * * * *" retries: 3 on_error: notify_webhook: - https://webhook.site/4b732eb4-ba10-4a84-8f6b-30167b2f2762
command requires arguments, please make sure to pass them as an array like in
Note that you can set
tz_location if the system time of where you run your service is not to your liking.
The core of
cheek consists of a scheduler that uses a schedule specified in a
yaml file to triggers jobs when they are due.
You can launch the scheduler via:
cheek run ./path/to/my-schedule.yaml
cheek run --help for configuration options.
cheek ships with a terminal ui you can launch via:
The UI allows to get a quick overview on jobs that have run, that error'd and their logs. It basically does this by fetching the state of the scheduler and by reading the logs that (per job) get written to
$HOME/.cheek/. Note that you can ignore these logs, output of jobs will always go to stdout as well.
All configuration options are available by checking out
cheek --help or the help of its subcommands (e.g.
cheek run --help).
Configuration can be passed as flags to the
cheek CLI directly. All configuration flags are also possible to set via environment variables. The following environment variables are available, they will override the default and/or set value of their similarly named CLI flags (without the prefix):
There are two types of event you can hook into:
on_error. Both events materialize after an (attempted) job run. Two types of actions can be taken as a response:
trigger_job. See the example below. Definition of these event actions can be done on job level or at schedule level, in the latter case it will apply to all jobs.
on_success: notify_webhook: - https://webhook.site/e33464a3-1a4f-4f1a-99d3-743364c6b10f jobs: coffee: command: this fails # this will create on_error event cron: "* * * * *" on_error: notify_webhook: - https://webhook.site/e33464a3-1a4f-4f1a-99d3-743364c6b10f beans: command: echo grind # this will create on_success event cron: "* * * * *"
Webhook are a generic way to push notifications to a plethora of tools. You can use it for instance via Zapier to push messages to a Slack channel.
Check out the
Dockerfile for an example on how to set up
cheek within the context of a Docker image.
cheek reports minimal usage stats. Each time a job is triggered a simple request that (only) contains your
cheek version is send to our servers. Check out the exact implementation here. Note that you can always opt-out of this by passing the
Thanks goes to:
- gronx: for allowing me not to worry about CRON strings.
- Charm: for their bubble-icious TUI libraries.
- Sam & Frederik: for valuable code reviews / feedback.