– albertoarena.it - submitted by Alberto Arena
A live, zoomable ER diagram of your Laravel app's actual database schema, safe to run in production because it only ever reads structure, never rows.
Read more [albertoarena.it]
– ashallendesign.co.uk - submitted by Ash Allen
Read about how to use the Illuminate\Console\Prohibitable trait to prevent destructive commands from running in your Laravel application. We'll also look at how to prevent your own custom Artisan commands from running using this trait.
Read more [ashallendesign.co.uk]
Join 9,500+ smart developers
Get my monthly newsletter with what I learn from running Spatie, building Oh Dear, and maintaining 300+ open source packages. Practical takes on Laravel, PHP, and AI that you can actually use.
No spam. Unsubscribe anytime. You can also follow me on X.
"Freek publishes a super resourceful and practical newsletter. A must for anyone in the Laravel space"
– albertoarena.it - submitted by Alberto Arena
Laravel event sourcing generator adds a new Artisan command that can generate a full domain directory structure for Spatie event sourcing.
Read more [albertoarena.it]
– geoligard.com - submitted by Goran Popović
While Supervisor is commonly used with queue-related commands, there is nothing stopping you from using Supervisor to run and monitor your own custom commands.
Read more [geoligard.com]
You should consider using the handle() method for dependency injection in Artisan commands, rather than __construct().
Read more [ides.dev]
– fly.io - submitted by Chris Fidao
We see how Laravel queues handle graceful restarts/stops, and how we can do the same in our own Artisan commands.
Read more [fly.io]
Christoph and I did another casual artisan call do talk about what's been keeping us busy.
You can easily add new information to Laravel's new "About" command
Read more [james.brooks.page]
Here's a cool technique by Aaron Francis where he uses artisan commands to create daemons.
Read more [aaronfrancis.com]
In the second part of this stream, I'll walk you through the inner workings of our new spatie/laravel-artisan-dispatchable package.
When you cancel a long-running artisan command with Ctrl+C, a SIGINT signal is sent by the operating system to the PHP process. You can use this signal to perform some cleanup quickly.
Symfony 5.2 introduced support for handling signals in commands.
We've released a package called spatie/laravel-signal-aware-commands that provides a substantial improvement to how you can use these signals in a Laravel app. In this blog post, I'd like to tell you all about it.
– ryangjchandler.co.uk - submitted by Ryan Chandler
When distributing console commands in a package or within an application, making sure data is in the correct format can be important. Let's build a make:user command that takes advantage of Laravel's validation helpers.
Read more [ryangjchandler.co.uk]
Using the newly released spatie/laravel-remote package, you can quickly execute Artisan commands on a remote server.
Here's an example that will clear the cache on the remote server.
php artisan remote cache:clear
In this blog post, I'd like to tell you all about it!
✨Laravel Package Tip: Hide your install commands from `php artisan` after installed to keep things tidy. pic.twitter.com/o4PK8xXkIk
— Brian Dillingham (@im_brian_d) January 2, 2021
Using our spatie/laravel-short-schedule package you can schedule commands at sub-minute intervals.
Aren't you tired of having to think about which artisan command to execute? The spatie/laravel-random-command package takes that pain away. It provides a random command that will pick a random command and execute it.
In this small blog post, I'd like to give you a couple of tips to make your Artisan commands better.
???
— Jeff Ochoa (@Jeffer_8a) April 24, 2019
A small trait to run use progression bars in @laravelphp commands#Laravel #PHP pic.twitter.com/lvGylb5QXm
Read more [twitter.com]
If you execute an Artisan command and something goes wrong, the error output is not terribly detailed.
You can improve the output slightly by tagging on -vvv to make to output more verbose.
Now we already know the line that where the problem originates: there's something going wrong on line 41 of the MyBrokenCommand command.
But we can improve the error output still. Nuno Maduro coded up a fantastic package called Collision that, once installed, provides much nicer output.
In this output we can immediately see what the silly programmer did wrong.
Let's hope that a future version of Laravel will be able to spit out these nicely formatted errors out of the box.
