Using Drush cron on Acquia Cloud Platform environments¶

Running Drush cron directly¶

You can execute alternative Drush cron commands using the following syntax on Acquia Cloud Next infrastructure:

/usr/local/bin/drush10 --uri=http://[site-uri] --root=/var/www/html/docroot -dv cron &>> /shared/logs/drush-cron.log

For environments running on Cloud Classic infrastructure, the syntax is as follows:

/usr/local/bin/drush10 --uri=http://[site-uri] --root=/var/www/html/${AH_SITE_NAME}/docroot -dv cron &>> /var/log/sites/${AH_SITE_NAME}/logs/$(hostname -s)/drush-cron.log

In the preceding example, &>> /var/log/sites/${AH_SITE_NAME}/logs/$(hostname -s)/drush-cron.log logs the cron output to a drush-cron.log file in the infrastructure’s logs directory.

Cron jobs must always include a logging statement.

Triggering a cloud hook through Drush cron¶

For infrastructure where you want a single hook, you can also run a specific cron hook directly. The command structure will vary based on your Drupal version and module. For example, for environments running on Acquia Cloud Next infrastructure, you might use:

/usr/local/bin/drush10 --root=/var/www/html/docroot -v ev "mymodule_cron();"  &>> /shared/logs/drush-cron.log

For environments running on Acquia Cloud Classic infrastructure, you might use:

/usr/local/bin/drush10 --root=/var/www/html/${AH_SITE_NAME}/docroot -v ev "mymodule_cron();"  &>> /var/log/sites/${AH_SITE_NAME}/logs/$(hostname -s)/drush-cron.log

The previous commands will log output to the standard log files, ensuring log rotation and maintenance continues.