Category: Laravel, Laravel

James Bannister • February 11, 2019 • 3 minute read Getting started is pretty easy, the documentation covers this in detail and there's a tonne of tutorials out there if you need further help getting started.

You make a few actions to fire off a few queued jobs and then you check your Horizon dashboard and see this: Horizon is running, there are jobs queued, but there are not queue workers running.

This prevents multiple instances of Horizon (occurs if you are running more than one Laravel application per server with Horizon running) competing for jobs from other Laravel applications. By following this approach, and updating our config/queue.php file appropriately, we ensure that we are pushing our queued jobs to a queue specific to that Laravel instance we are running and that our Horizon instance is only completing jobs on that queue: With both of these approaches implemented, you'll have Horizon running across all of your application environments and projects, as well as the ability for them all to run on the same server, with multiple instances of Horizon running.
Newsletter

Get the latest Laravel/PHP jobs, events and curated articles straight to your inbox, once a week

Fathom Analytics | Fast, simple and privacy-focused website analytics. Fathom Analytics | Fast, simple and privacy-focused website analytics.
Achieve superior email deliverability with ToastMail! Our AI-driven tool warms up inboxes, monitors reputation, and ensures emails reach their intended destination. Sign up today for a spam-free future. Achieve superior email deliverability with ToastMail! Our AI-driven tool warms up inboxes, monitors reputation, and ensures emails reach their intended destination. Sign up today for a spam-free future.
Community Partners