Skip to main content
tinymash
  • Screen mode

Scheduled work

Use the operating system's scheduler for predictable publication and maintenance. Run commands from the installation root as the same operating-system user that owns the tinymash runtime.

Recommended cron entries

Publish due content every minute and run housekeeping every 15 minutes:

* * * * * cd /var/www/tinymash && /usr/bin/php8.4 bin/tinymash.php content:publish-due >/dev/null 2>&1
*/15 * * * * cd /var/www/tinymash && /usr/bin/php8.4 bin/tinymash.php housekeeping:run >/dev/null 2>&1

Adjust the installation path and PHP binary for the host. The release also includes samples/cron/tinymash.cron.

Use the same operating-system user for cron and the PHP-FPM pool. CLI housekeeping can then clean import staging files created by web requests.

Scheduled publication needs content:publish-due at the resolution you expect. The web fallback does not publish scheduled entries.

Housekeeping

Housekeeping performs bounded core cleanup and calls registered tasks from active plugins. Depending on current settings and installed features, this can include stale drafts, Trash retention, revisions, notifications, cache work, temporary import workspaces, and plugin queues.

Inspect the current policy and last recorded run:

php8.4 bin/tinymash.php housekeeping:status

Run core housekeeping without plugin tasks when diagnosing a plugin problem:

php8.4 bin/tinymash.php housekeeping:run --no-plugins

Some plugins also provide a dedicated queue command when their work needs a shorter interval than general housekeeping. Use the plugin's command help for that schedule.

Web fallback

System > Security > Web cron fallback can run throttled housekeeping after ordinary public GET or HEAD requests when cron is unavailable. It is traffic-dependent and not a precise scheduler.

Use OFF when reliable cron is installed. Use AUTO only as a fallback for hosts without a dependable scheduler.

Do not discard cron output until a new schedule has been tested. Record failures through the host's mail, journal, or a protected log, and review them after upgrades.