- Is glorpen/queue-bundle a Laravel package?
- No. glorpen/queue-bundle is a Symfony bundle that integrates queue-interop messaging into Symfony applications through DI container configuration. It defines transports, connections, and consumers for Symfony, not Laravel. There is no Laravel service provider, facade, or framework integration included.
- Can I install glorpen/queue-bundle in a Laravel application?
- You technically could add it via Composer, but it would not wire into Laravel's container, queue system, or console kernel. Making it work would require a custom service provider, DI translation, and event-dispatcher reconciliation that your team would own permanently. For Laravel, the native queue system already covers this use case, so integration is not recommended.
- What Laravel version does glorpen/queue-bundle support?
- None. The package targets Symfony, and an unmaintained bundle of this vintage will likely pin PHP 5.x or 7.x and Symfony 2.x or 3.x constraints. A Composer dry-run against a PHP 8.x Laravel runtime is the fastest gate and should be done before any further evaluation. If it does not resolve, close the ticket.
- What is glorpen/queue-bundle used for?
- It gives Symfony applications a configuration-driven way to define queue transports, connections, and consumers through YAML or PHP config. It wires producer services for dispatching messages and consumer services as console commands or workers. It supports multiple queue backends through queue-interop factories and allows custom serializers and middleware.
- What license does glorpen/queue-bundle use?
- The package is GPL-3.0, which is strong copyleft. For a proprietary or SaaS product, that creates derivative-work exposure that legal teams typically reject. Route the license question to legal before spending estimation cycles; absent a clear ruling, the package is blocked regardless of technical merit.
- Is glorpen/queue-bundle actively maintained?
- There is no visible maintainer, release cadence, adoption base, or security response path. It shows zero stars and zero dependents, so there is no production evidence or issue corpus to rely on. Every edge case and future obligation would land on your team by default.
- What are the best alternatives to glorpen/queue-bundle for Laravel?
- Use Laravel's first-party queue system: make:job, ShouldQueue, dispatch(), and a configured queue connection. Pair it with Horizon for supervision and metrics and failed_jobs for retry visibility. This delivers the same async processing outcome with active maintenance and no third-party dependency.
- How do I configure async queues in Laravel without this package?
- Set your queue connection in config/queue.php and the QUEUE_CONNECTION environment variable, choosing database, Redis, SQS, or another supported driver. Generate a job with php artisan make:job, implement ShouldQueue, and dispatch it from your application code. Run php artisan queue:work or Horizon to process jobs in the background.
- Does glorpen/queue-bundle support multiple queue backends?
- Yes, it supports multiple queue backends through queue-interop factories, but that capability is irrelevant on a Laravel stack. Laravel already supports database, Redis, SQS, and other drivers natively with first-party documentation. There is no capability gap this package closes for Laravel applications.
- Should I fork glorpen/queue-bundle to use it with Laravel?
- Forking means taking permanent ownership of an abandoned Symfony codebase and writing a Laravel integration layer yourself. Compare that ongoing allocation against the hours needed to write equivalent Laravel jobs with ShouldQueue and dispatch. Unless a named business requirement demands interoperability with an existing Symfony service, substitution is the cheaper and safer path.