Install
Works with Drupal: ^11 || ^12Using Composer to manage Drupal site dependencies
Alternative installation files
Download tar.gz
85.88 KB
MD5: a49fcefd365bef594f22ae34296fe64c
SHA-1: 16ae027652d68bb9f740ed771d58b23eddd3dd6c
SHA-256: 1e12114e06f27aa0d00dc05f980dcdad7047ea97f3d0ede0f2a90011a2cc2b77
Download zip
119.16 KB
MD5: ef2fd656382ce6623572233bcbff720c
SHA-1: c09ba1677fab4859dcbc137e91a4349a7970ba66
SHA-256: 6ac431756cbd9909a70497914b29cac4ad84ec263c909b8bfdff3d9c5e3c8922
Release notes
New: wake a job
- The site can ask the worker to run a job now, rather than at its next turn:
\Drupal::service('druker.wake')->wake($job), ordrush druker:wake 12. The job starts within a second or two. - A signal is an empty file named after the job, in
$settings['druker_wake_dir']. By default that isprivate://druker/wake, or a directory of the site's own undertemporary://;FALSEswitches waking off. The worker learns the directory from the schedule (wake_dir). - Each signal runs the job once, even with several workers sharing the directory. A running job runs again when it finishes; a job that allows overlap starts alongside. Schedules are unchanged.
drush druker:checksays when waking is off or the directory cannot be written.
Upgrading
- Rebuild and redeploy the worker binary. A worker from 1.0.2 runs as before and does not wake.
- The worker must share the wake directory with the site and run as the site's user. On one machine or a shared private file system, there is nothing to set.
- No update hook.
Issue: #3637503