Profiles per project
Name them: “Everything”, “Just emails”, “Like production”. Each remembers its own settings.
Save how your queues should run — which queues, in what order, with what limits and how many workers — and start the lot with one press. One button stops the group.
Free for everyone · macOS 14 Sonoma or later · Apple silicon and Intel
php artisan queue:work redis --queue=critical,default,low --memory=512 --timeout=90 --tries=3
Name them: “Everything”, “Just emails”, “Like production”. Each remembers its own settings.
List queues in the order they should be worked — critical before default before low.
Run three workers on one profile, shown as “emails ×3” and stopped together.
Change code under app/ while workers run and devCommand nudges you, because a worker holds old code in memory.
Connection, queues, memory, timeout, tries, sleep, max jobs, max time and stop-when-empty. Only the flags you change are written into the command.
php artisan queue:work redis --queue=critical,default,low --memory=512 --timeout=90 --tries=3
Each worker gets its own terminal tab, so you see every job as it’s processed — and which one failed.
php artisan queue:work redis --queue=critical,default,low --memory=512
Running
Restart
Kill
devCommand watches app/ with FSEvents while workers run. Save a job class and it tells you the workers need restarting.
php artisan queue:work redis --queue=critical,default,low --memory=512 --timeout=90 --tries=3
The small things
schedule:work is a button of its own, beside your workers.
queue:failed lists them; queue:flush asks before it clears them.
Start a profile without opening the window.
--run "Just emails" starts a profile by name.
database, redis, sqs — whatever your .env says, or override it per profile.
Stopping a group stops every worker’s whole process tree.
Keep exploring
No account, no licence key. Point devCommand at ~/Sites and press your first command.
macOS 14 Sonoma or later · Apple silicon and Intel · Version 1.0