Reference

The lookup tables the usage guide points at. A content root is a set of self-contained cron directories; a cron's schedule lives in its settings file. These pages spell out that settings format, the handler a cronhoster-cron-handler.js fulfils, the commands that drive the local scripts and server, and every path that can live in a content root, so each guide page can link to one source of truth.

Settings →

The cronhoster-cron-settings.json format: the named runs, every time field and its range, the wildcard, and the concurrency ceiling.

Scripts →

The handler contract: how cronhoster-cron-handler.js is run, the command-line arguments it receives, success and failure semantics, and how require resolves.

Commands →

The local CLI flags and the server-side service commands: starting, restarting and inspecting the API and runner, and pulling logs back.

Files →

The content-root layout: naming rules, the ignore rules, and sync-once immutability; each path shown as a pattern.

The shape of a content root

One folder of self-contained cron directories. Each top-level directory is a cron; its cronhoster-cron-handler.js is the entry point, its cronhoster-cron-settings.json is the schedule, and everything beside them rides along as its own code.

<cronhoster-config-contentRoot>/    your content root
  digest/                          a cron
    cronhoster-cron-handler.js     the entry point
    cronhoster-cron-settings.json  when it runs
    format.js                      a module it imports
  backup/                          another cron
    cronhoster-cron-handler.js
    cronhoster-cron-settings.json
  _digest/                         ignored (leading _ = local only), the next version
  .gitignore                       ignored (dotfile)

The Files page breaks this down path by path; the Settings page is the format behind each cron's schedule.