Package Data | |
---|---|
Maintainer Username: | dusterio |
Maintainer Contact: | denis@mysenko.com (Denis Mysenko) |
Package Create Date: | 2017-04-11 |
Package Last Update: | 2018-02-12 |
Language: | PHP |
License: | MIT |
Last Refreshed: | 2024-11-11 15:15:06 |
Package Statistics | |
---|---|
Total Downloads: | 6,292 |
Monthly Downloads: | 0 |
Daily Downloads: | 0 |
Total Stars: | 6 |
Total Watchers: | 2 |
Total Forks: | 1 |
Total Open Issues: | 0 |
Package that adds verbosity to Laravel/Lumen built-in console commands
Even though Laravel console commands have verbosity flags -v/-vv/-vvv
they are actually ignored. Therefore, using some of the console commands leaves developer completely blind – you have no idea what's happening behind the scenes.
Example running queue:work
without this package:
$ php artisan queue:work --once
$
What? Did it work or not? Was there a job in the queue or not? Why did it take several seconds to complete - does it mean it actually worked? What queue or connection did it use because I don't remember if I set them correctly?
Reminds of Microsoft products uh? :)
Example running queue:work
after installing this package:
$ php artisan queue:work -vv
Using connection: sqs
Using queue: live-visits
The queue seems to be empty.
Sleeping for 3 seconds.
Let's now break AWS credentials so that SQS is unreachable:
$ php artisan queue:work -vv
Using connection: sqs
Using queue: live-visits
Error executing "ReceiveMessage" on "https://sqs.ap-southeast-2.amazonaws.com/XXX/live-visits"; AWS HTTP error...
Couldn't fetch a job from the queue. See the log file for more information.
Voilà! Now I know exactly what happened in both cases, and now -vv
flag did exactly what it was supposed to do.
$ composer require dusterio/laravel-verbose
Then add a service provider to your config/app.php
:
/* ... */
Dusterio\LaravelVerbose\Integrations\LaravelServiceProvider::class,
/* ... */
So far tested with:
queue:work
only at the moment)queue:work
queue:listen