- Is roslov/queue-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. The release ships a Symfony bundle class and DI extension/service wiring rather than a Laravel ServiceProvider, publishable config, or a config/queue.php driver. To use it from Laravel you would either depend on the framework-agnostic core directly or write a thin service provider that bridges the Symfony services.
- How do I install and register roslov/queue-bundle?
- Install it with Composer using require roslov/queue-bundle, then register the bundle in your Symfony bundles configuration. Laravel does not auto-discover Symfony bundles, so installation alone will not wire it into a Laravel application. In Laravel you must add your own provider or use the underlying queue component standalone.
- Which Laravel and PHP versions does roslov/queue-bundle support?
- There is no documented Laravel support matrix, and the package is Symfony-targeted. The CI matrix exercises PHP 8.4 and 8.5, but no Laravel version support statement is published. Validate compatibility against your pinned framework and component versions before adopting it.
- How do I dispatch a background job and run a queue worker?
- You dispatch messages to a configured queue backend from application code, then run dedicated CLI worker processes that consume and hand messages to your registered job handlers. Business logic lives in extensible handler classes, keeping HTTP requests free of time-consuming work. In Laravel you would normally wrap the worker in an artisan command or a supervised process manager.
- How do I configure the queue backend and job handlers?
- Configuration goes through the bundle's Symfony configuration and service container, where you select the queue backend and register handlers. Adapting a different backend is a matter of changing the bundle configuration rather than rewriting dispatch code. For Laravel you would need to map this configuration into your own config file and container bindings.
- What changed in roslov/queue-bundle 2.2.1?
- It is a maintenance patch covering coding style, editorconfig and gitattributes hygiene, a README dependency refresh, and grammar fixes, plus PHP 8.4 and 8.5 added to the test matrix. The one behavioural item is a fix to the exception shortener, which can change how exceptions are rendered or truncated. No public API changes are signalled.
- Is roslov/queue-bundle 2.2.1 a safe drop-in upgrade from 2.2.0?
- As a semver patch it is expected to be drop-in, but treat the exception shortener as the only behavioural delta. Pin 2.2.1 on a branch, run the full test suite and a container-boot smoke test, and diff exception output against your error-monitoring fingerprints. Keep a documented rollback to 2.2.0 before promoting.
- Can I use roslov/queue-bundle in a Laravel app without building a bridge?
- Not cleanly, because the bundle surface targets Symfony's container and configuration model. The preferred path is to confirm whether the underlying queue core is usable standalone and depend on that directly. Only introduce the bundle plus a thin Laravel provider if the core proves unusable on its own, and keep that bridge behind an internal interface.
- Is roslov/queue-bundle production-ready, and who maintains it?
- Technical risk from the release itself is low, but stewardship is effectively single-maintainer with community-only support and no vendor SLA. Any Laravel adapter you build becomes yours to maintain across framework upgrades. Pilot one non-critical consumer in staging for a full release cycle before wider production use.
- What are the alternatives to roslov/queue-bundle for async queues in Laravel?
- Laravel's native queue system with database, Redis, or SQS drivers is the default choice, with Horizon for Redis monitoring. Symfony Messenger is the comparable option on the Symfony side. Evaluate whether the standalone roslov queue component adds enough value over native tooling to justify an extra dependency.