- How do I install jeffersongoncalves/laravel-queue-worker in a Laravel app?
- Install it with Composer by running composer require jeffersongoncalves/laravel-queue-worker. Laravel's package auto-discovery registers the service provider, so manual wiring is normally unnecessary. If the package ships a config file, publish it with vendor:publish so you can adjust worker options such as queue, connection, timeout and retries.
- Can I run Laravel queue workers without Supervisor using this package?
- Yes. The package is built to start, stop, restart and monitor workers from your own application or Artisan, so you do not need a Supervisor daemon watching the process. That makes it practical on shared hosting and small single-server deployments where installing Supervisor is impossible or overkill. Keep in mind that Supervisor still offers stronger process supervision and automatic restart guarantees for large production fleets.
- Which Artisan commands does the package add for starting and stopping queue workers?
- The package exposes Artisan commands to start, stop, restart and check the status of queue workers, and the same operations are available through the service container. You can pass worker options such as queue, connection, timeout and retries when launching a worker. Use the status command to confirm a worker is alive before assuming jobs are being processed.
- Which Laravel and PHP versions are supported?
- Check the composer.json requirements in the repository before installing, since the package targets specific Laravel and PHP version ranges. Because it is a thin layer over Laravel's own queue system, its behaviour follows the framework version you run, but that does not guarantee the constraint allows older releases. Verify the requirement rather than assuming compatibility with an unsupported Laravel version.
- How do I configure the queue connection, queue name, timeout and retries for a worker?
- Worker options come from the package configuration file and can be overridden per worker when you start it. Typical options include the queue connection, queue name, timeout, number of tries and sleep interval, mirroring the flags on queue:work. Publish the config and set values that match your environment instead of relying on defaults.
- Can I start a queue worker from application code instead of the command line?
- Yes. The package integrates with Laravel's service container, so you can resolve the worker manager and start or stop workers from a controller, command, scheduled task or test. This is useful when worker lifecycle should follow application logic, for example starting a worker before a batch of jobs and stopping it afterwards. Be careful not to spawn duplicate workers from concurrent requests.
- Does it work with Redis, database and SQS queue connections?
- The package does not implement its own queue backend; it drives Laravel's queue workers, so any connection Laravel supports can be used, including Redis, database, SQS and Beanstalkd. Driver-specific behaviour such as visibility timeouts and retry semantics still comes from Laravel and your queue service, not from this package. Test the connection you plan to use in staging before relying on it.
- Is this package a replacement for Laravel Horizon or Supervisor?
- Horizon is a full Redis queue dashboard and supervisor with metrics and auto-balancing, while Supervisor is a general purpose process monitor. This package is much lighter: it lets your application start, stop and monitor workers without an external daemon. Choose it for small deployments, scheduled tasks and test environments, and prefer Horizon or Supervisor when you need resilience and observability at scale.
- Can I use it for testing queued jobs in my test suite or CI pipeline?
- Yes. Because workers can be started and stopped from code, the package is handy in test suites and CI pipelines where you want to process queued jobs on demand without a background daemon. Start a worker, run your assertions or console commands, then stop it. Pair it with Laravel's queue fakes when you only need to assert that a job was dispatched.
- How do I restart queue workers after deploying new code?
- Restart workers after every deploy so they pick up updated classes, since long-running PHP processes keep the old code in memory. The package's restart command stops the running worker and starts a fresh one with your configured options. Wire the restart into your deployment script and confirm the worker is running again before traffic hits the new release.