Commands

Two surfaces: the local command you run on your own machine to sync your crons and pull logs, and the service commands you run on the server to manage the API and the runner. The local command is the one you use daily; the server commands are for setup and the occasional check-in.

cronhoster-local.js

The one command in the local package. It reads your config.json, then runs each step you ask for, in order: the sync first, then each log browser. A run does its work once and exits.

node cronhoster-local.js --config /path/to/config.json --all
Sync your crons and build every log browser in one run.
FlagMeaning
--config <path>Required. The full absolute path to your config, a .json file.
--syncUpload every cron directory the server does not have yet, and remove any you have deleted locally. See Sync.
--web-logsMirror the access log and build the Web Logs browser.
--server-logsMirror the health samples and build the Server Logs browser.
--cron-logsMirror the run records and build the Cron Logs browser.
--allAll four steps above.

The pages land under your cronhoster-config-tools folder; the Tools section shows what each one looks like. To sync on a timer, run the command from your own scheduler.

Server-side services

The installer lays down two systemd units. Manage them with ordinary systemctl; they run as a dedicated non-root user.

# is the sync API healthy?
systemctl status cronhoster-api

# is the scheduler running your crons?
systemctl status cronhoster-runner

# restart the scheduler
sudo systemctl restart cronhoster-runner
Check and restart the two services.
CommandPurpose
systemctl status cronhoster-apiHealth of the localhost sync API that the local package uploads to.
systemctl status cronhoster-runnerHealth of the scheduler that discovers crons and runs their handlers on time.
systemctl restart cronhoster-apiRestart the sync API, for example after the token changes.
systemctl restart cronhoster-runnerRestart the scheduler. In-flight runs stop, and times that pass while it is down are skipped.
journalctl -u cronhoster-runnerThe service's own journal: its starts and stops, and one line per cron added, removed or broken. Per-run detail lives in the run records.

Each run is captured as a structured record (duration, exit code, and the tail of its stdout/stderr), written to dated day-files server-side, pruned after fourteen days, and shown per run in the Cron Logs tool.