Updates and scheduled tasks

Stay on the newest verified release, and run tasks on a cadence.

Updating

/update installs the newest release. The welcome screen and the browser's sidebar tell you when one exists. The download must match the release's SHA256SUMS or nothing is installed. A gateway started with -serve restarts itself on the new binary; an interface tells you to restart it.

The gateway reports its own build through motita gateway status, so after installing over an old binary you can tell whether the process still running is the previous one.

Releases are cut automatically from semantic commits: feat bumps the minor version, fix the patch, and a breaking change the major. The newest version is always shown on the home page.

Scheduled tasks

A scheduled task is a task or a plan the gateway submits on its own, on a cadence, with nobody at the keyboard. Each one is a small JSON file in ~/.motita/schedules/ that you can read and edit by hand.

• The cadence is a duration (30m, 6h, 24h), not cron syntax. every 6h means six hours after the last run.
• The shortest allowed cadence is one minute (schedule.min_every).
• A task can be a plan (read-only) or a task, and can be pinned to a session.
• Create, change, run-now and delete them through /v1/schedules, or from the interface.

curl -s -X POST -H "Authorization: Bearer $TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"title":"nightly audit","task":"check the logs and report","kind":"plan","every":"24h"}' \
  http://127.0.0.1:7477/v1/schedules

Go deeper

• Reference: scheduled tasks
• Guide: automatic releases