Crusust

Scheduled jobs & cron

Scheduled jobs, done right.

Crusust runs your recurring and one-off jobs on time, retries the ones that fail, and shows you exactly what ran and when.

Read the documentation →$ crusust serve
crusust — shell
# start the scheduler
$ crusust serve --data ./jobs

# register a nightly job
$ curl -X POST /v1/jobs \
    -d '{"cron":"0 3 * * *","url":"..."}'
→ scheduled · id job_2

# list recent runs
$ curl /v1/jobs/job_2/runs

Capabilities

Cron & one-off

Schedule with cron syntax or fire a job once at a future time — both are first-class.

Retries with backoff

A job that fails is retried on a policy you set, and lands in a dead-letter list if it keeps failing.

Run history

Every run is recorded with its status and duration, so you can see what happened without grepping logs.

Crusust Scheduled·Cron & one-off·Retries·Run history·REST API

Schedule once, runs forever.

Register a job with a schedule; Crusust triggers it and tracks each run.

  1. 1Start Crusust on any host.
  2. 2Register a job with a cron schedule.
  3. 3Watch runs and retries over the API.
# start the scheduler $ crusust serve --data ./jobs # register a nightly job $ curl -X POST /v1/jobs \ -d '{"cron":"0 3 * * *","url":"..."}' → scheduled · id job_2 # list recent runs $ curl /v1/jobs/job_2/runs