icemix/nodaemon

Batch process Laravel Queue without a daemon; Processes queue jobs and kills the process

0.1 2020-04-30 06:34 UTC

Requires (Dev)

• mockery/mockery: ^1.1
• orchestra/testbench: ^4.0
• phpunit/phpunit: ^8

MIT

• ETTA EGBE JOSEPH

• queue
• laravel

README

Introduction

Batch process Laravel Queue without a daemon; Processes all jobs on the queue(s) and exits without running on daemon mode. This is useful in cases where you just want to process jobs on the queue and exit the worker process so they don't pile up in memory.

Installation

To install the latest version of NoDaemon, simply use composer

Download

composer require icemix/nodaemon

• If your Laravel version is below 5.5, you'll need to add the service provider to your config/app.php file.

Queueworker\NoDaemon\NoDaemonServiceProvider::class,

Usage

NoDaemon is a console application that extends the functionality of laravel's WorkCommand - Illuminate\Queue\Console\WorkCommand. See Laravel Queue documentation.

To run the queue worker sans-daemon mode, simply add the --nodaemon option to the original laravel queue worker command:

php artisan queue:work --nodaemon

Argument and Options

Since this package extends laravel's WorkCommand, it takes exactly all the arguments and options the original WorkCommand takes with three added options:

• --nodaemon option tell the worker to process jobs on the queue without running in daemon mode.
• --jobs (default: 0, optional) - It allows you to specify the number of jobs to process each time the command runs. The default value 0 means it'll process all available jobs in the queue.
• --max_exec_time (default: ini_get('max_execution_time') - 5s, optional) - On some webhosts, your scripts will be killed, if it exceeds some amount of time. To prevent this behavior on really full queue, worker will stop after --max_exec_time. This is especially useful if you're running this command via your application's route or controller. See Laravel Documentation on how to run your queue programmatically.

Note on --max_exec_time

• 0 (zero) means the worker will run forever, which in this context means until the worker process is done. This is the default behavior when run from CLI.
• This option will not prevent Maximum execution time exceeded error, it'll try to avoid it by not running the next job on the queue if the script is reaching its max_execution_time

Testing

composer test

License

MIT license (MIT) - Check out the License File for more.