# Manage Client - cron examples
#
# Adjust the paths and add with `crontab -e`.
# Check the PHP path with: which php
#
# --quiet suppresses normal output. Errors still go to STDERR and are
# delivered by cron via mail.

MAILTO=admin@example.org

# Nightly backup at 03:20.
20 3 * * * /usr/bin/php /var/www/myproject/manage-client/bin/manage-client.php backup --trigger=cron --quiet

# Status report to the Manage server, hourly at minute 7.
7 * * * * /usr/bin/php /var/www/myproject/manage-client/bin/manage-client.php heartbeat --quiet

# Update check on weekdays at 08:00.
# Exit code 2 means "update available" - cron doesn't report that on its
# own, hence the explicit mail here.
0 8 * * 1-5 /usr/bin/php /var/www/myproject/manage-client/bin/manage-client.php check --quiet || true

# Updates are deliberately NOT installed automatically.
# An update overwrites files while the application is live and can trigger
# migrations; that belongs under supervision. If it should be automated
# anyway, force a backup first:
#
# 30 2 * * 0 /usr/bin/php /var/www/myproject/manage-client/bin/manage-client.php backup --trigger=update --quiet && \
#            /usr/bin/php /var/www/myproject/manage-client/bin/manage-client.php update --yes --quiet