Overview
The Runjet user manual — where to start, how to install an agent, and where to find everything else.
Runjet schedules what runs when, and remembers how it went; the commands themselves are run by agents on your own machines. This manual is for the person using Runjet: jobs, runs, agents, accounts and workspaces. What Runjet promises to refuse, and what happens when you meet one of those refusals.
Three doors
- Starting out? Quick start is one pass from registration to a first run; What Runjet is is why it looks the way it does.
- Installing an agent? Installing an agent is the walk
from download to
systemctl enable --now, and When an agent will not run is what to do when something sticks. - Looking for one thing? ⌘K (on Windows Ctrl K) searches the whole manual; the glossary is the alphabet.
Chapters
| Chapter | What it covers |
|---|---|
| Jobs | the command, its schedule, agents, tags, secrets, missed runs, running by hand |
| Runs | states, output and retention, history, long-running jobs |
| Agents | installing, configuration, isolation, upgrading, resetting |
| Dashboard | the five bands and kiosk mode |
| Accounts and roles | roles, invitations, a forgotten password, your profile |
| Notifications | every email, when it goes and to whom |
| Workspace | registration, plans, its life, export, the audit log |
| Reference | cron, error responses, the glossary |
How this manual is written
The names of controls are given as the application spells them: click Register agent. Log lines and API responses are quoted verbatim so that they can be searched for. At the foot of every page is a line naming the files in Runjet's own source that the page is the reading of.