Get the latest Laravel/PHP jobs, events and curated articles straight to your inbox, once a week
Source: fly.io
Handling Signals in Laravel
Author Name Chris Fidao Social Media Image by https://annieruygtillustration.com/ During a deployment, you likely restart your queue workers using something like artisan queue:restart or supervisorctl restart
When a SIGTERM or SIGQUIT signal is received, the worker waits until the currently processing job finishes before actually stopping.
If instead I send it signal SIGTERM, it will finish the job and then exit: # Start a worker php artisan queue:work
# Dispatch a job, and then # kill the worker with SIGTERM # Process ID 69679 in my case kill -s TERM 69679
When a SIGTERM or SIGQUIT signal is received, the worker waits until the currently processing job finishes before actually stopping.
If instead I send it signal SIGTERM, it will finish the job and then exit: # Start a worker php artisan queue:work
# Dispatch a job, and then # kill the worker with SIGTERM # Process ID 69679 in my case kill -s TERM 69679
Newsletter
Glimpse
Glimpse streamlines Laravel development by seamlessly deploying GitHub pull requests to preview environments with the help of Laravel Forge.
Community Partners
Laravel/PHP Careers