Operations
Run operational commands from the tinymash runtime root with the operating-system user that owns the installation:
php8.4 bin/tinymash.php list
Use --help on a command for its arguments, options, constraints, and examples. See the CLI reference for the complete command list. A successful command exits with status 0; failures return a non-zero status.
Routine commands
system:statusreports the current runtime.content:publish-dueactivates due scheduled entries.housekeeping:statusreports housekeeping policy and last-run state.housekeeping:runperforms routine cleanup and active plugin housekeeping.cache:clearclears compiled templates, indexes, and public response caches.cache:warmprepares public listing caches.media:usagereports known media references.deploy:auditchecks managed application files against a release manifest.
Mutating CLI commands should not run as root. Root execution requires confirmation or the explicit --allow-root override and can leave files with ownership that prevents later web writes.
The normal operating baseline is simple: real cron for scheduled work, writable runtime paths with correct ownership, protected logs and backups outside public/, a stable PHP session name, clean release replacement, and a verified recovery path.
Backups, log review, available disk space, PHP-FPM health, cron output, mail delivery, TLS, web-server authentication, and plugin queues remain operator responsibilities outside ordinary page requests.
For a failed request or maintenance command, start with Troubleshooting.