Scheduler and monitoring
System cron, the cron URL or pseudo-cron, the jobs that run, /health for uptime monitors, and log files.
Running the jobs#
Jobs send email, expire checkouts, reconcile bank payments, build analytics, take backups, deliver outbound webhooks and publish the SEO files. Choose one way to run them:
System cron (preferred) — /etc/cron.d/billing:
* * * * * www-data php /var/www/encrypted.com/app/cli.php cron --data=/var/www/encrypted.com/data >/dev/null 2>&1
Then set 'cron' => ['mode' => 'system', …] in data/config.php so page views no longer run jobs.
The cron URL — when you cannot add a cron entry, call https://encrypted.com/cron.php?key=<cron.key from data/config.php> every minute from any scheduler.
Pseudo-cron — with neither, jobs run after page views, at most once a minute. Fine for a quiet test installation, not for production: with no visitors, no email goes out.
Super → Health & jobs shows which one is active, every job's schedule, last result and next run, and Run now.
Uptime monitoring#
Point an external monitor at https://encrypted.com/health (on a plain vhost: /index.php?r=health). It answers 200 with {"status":"ok"} when the database, data directory and scheduler are healthy, and 503 with the reason otherwise. On a two-server pair, /health/write, /health/read and /health/lease tell a load balancer which server can take which traffic.
Logs#
data/logs/— the application log, one JSON object per line. Errors shown to users carry a Reference that appears in the log./var/log/nginx/and the PHP-FPM log — requests and PHP-level errors.- The
logs.prunejob keeps the application logs to a reasonable size.
Alerts you will receive#
Super admins are emailed when: the daily self-check fails, a backup fails or is older than 26 hours, a restore drill fails, the system monitor finds a critical problem, GeoIP files go stale, or a workspace's dispute rate passes the alert level. Each alert is sent at most once a day (system monitor: every 6 hours).