Download the PHP package iivannov/elegant-laravel-worker without Composer
On this page you can find all versions of the php package iivannov/elegant-laravel-worker. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package elegant-laravel-worker
Elegant Laravel Worker for Laravel 5.3
Elegant way to gracefully handle SIGTERM signal in Laravel 5.3 queue worker. In Laravel >=5.4 this issue is beautifully handled.
Install
Via Composer
Register in Laravel
To replace the default Queue Worker with this one, you need to add the ElegantWorkerServiceProvider class to the providers array in your config\app.php
Use Case
Gracefully stop a Queue Worker by using SIGTERM signal.
Why would I stop the Worker?
There are many cases that will require to restart the worker.
- start/stop workers when auto-scaling
- temporarily stop the execution of tasks
- reloading supervisor (or another monitoring tool) configuration
Default Laravel Behaviour:
When SIGTERM is received by the Worker it interrupts immediately the currently processed job, which may break your application by not letting the job finish leading to unexpected results.
Elegant Behaviour:
When SIGTERM is received by the Worker it will wait for the currently processed job to finish and then will exit gracefully.
What do we solve?
- Interrupting long running jobs executing consecutive interrelated tasks
- Interrupting in the middle of a DB transaction causing a deadlock
- Prevent repeating the execution of a an interrupted job when it is picked up again by a Worker
