gocron

A task scheduler built with Go and Vue.js that allows users to specify recurring jobs via a simple YAML configuration file. The scheduler reads job definitions, executes commands at specified times using cron expressions, and passes in environment variables for each job.

Runssource: GitHubGoMITcommit 70e57b9895b9

Go, MIT licensed. The project labels itself: backup, backups, cron, docker, golang, oidc, schedule and scheduler.

gocron runs. An Argusic agent installed it in 2 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

GoCron builds, all 13 test packages pass, and the server serves the health endpoint at 200, serves the web UI at 200, and executes scheduled jobs with full logging to SQLite.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
1
last tested
stars
626
forks
22
open issues
2
watchers
2
size
16 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Install time
2 minutes
Cold machine to finish
5 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
curl -s http://127.0.0.1:8156/health returned 200; curl -s -X POST http://127.0.0.1:8156/api/jobs/example-scheduled-happy-path returned 204; curl -s http://127.0.0.1:8156/api/runs/example-scheduled-happy-path returned full run with successful log output including 'start', 'Sat Oct 17 04:20:43 UTC 2026', and 'done'; go test ./... exited 0 with 13 packages passed
Model tokens used
112,928
Exact commit tested
70e57b9895b9
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

ok    github.com/flohoss/gocron/internal/software  0.011s
ok    github.com/flohoss/gocron/internal/webui  (cached)
ok    github.com/flohoss/gocron/pkg/expand  (cached)
ok    github.com/flohoss/gocron/services  1.308s
?     github.com/flohoss/gocron/services/jobs  [no test files]
exec
/bin/sh -lc 'pkill -f /tmp/gocron 2>/dev/null; echo "cleaned up"' in /work/repo
 exited 143 in 0ms:
All 13 test packages pass, the server starts, health endpoint returns 200, job execution works end-…
tokens used
112,928
All 13 test packages pass, the server starts, health endpoint returns 200, job execution works end-…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 2 minutes, faster than the median of the 47 comparable projects Argusic has measured.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 48 backup projects Argusic has installed and timed, gocron was the 11th fastest to reach a running state, and 32 of 48 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 2 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.02

Topics (from GitHub)

backupbackupscrondockergolangoidcscheduleschedulertaskvue

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/gocron.svg)](https://argusic.com/subject/gocron)

Questions

Does gocron run?
Yes. gocron runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test gocron?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 70e57b9895b9. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test gocron?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does gocron take to install?
2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does gocron need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing gocron?
Nothing did, in the recorded run: zero errors between clone and running.
How does gocron compare with the alternatives?
Of the 48 backup projects Argusic has installed and timed, gocron was the 11th fastest to reach a running state, and 32 of 48 reached one at all.
Where is the evidence for gocron?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion