- Is mcfedr/queue-manager-bundle a Laravel package?
- No. It is a Symfony bundle that registers through Symfony's kernel, DI container, configuration tree, Twig templates, and routing. It provides a web UI for managing AMQP/RabbitMQ-style queues, but it does not integrate with Laravel's queue abstraction.
- Can I install mcfedr/queue-manager-bundle in a Laravel application with Composer?
- You can run composer require, but a working integration is a dead end. Laravel ships some Symfony components such as console and routing, but not symfony/framework-bundle, and standing up a second Symfony kernel inside a Laravel process is not a supported configuration. Treat this as a Symfony-only package.
- What does mcfedr/queue-manager-bundle actually do?
- It adds a web interface for inspecting queues and exchanges, monitoring and controlling consumers, and running worker daemons. It is built on the queue-manager library for AMQP/RabbitMQ-style queues. Think of it as an operator console for a Symfony-based queue stack.
- Does queue-manager-bundle work with Laravel Horizon or the failed_jobs table?
- No. Laravel's queue model uses its own drivers, payload envelope, failed_jobs table, and queue:retry and queue:forget tooling. The bundle operates on a different abstraction and does not read or write Laravel's queue data structures. You cannot use it as a drop-in Horizon replacement.
- How can I use queue-manager-bundle alongside a Laravel application?
- The realistic path is to run it as a small standalone Symfony service in front of the same broker. That preserves the package as shipped, but both runtimes must agree on the wire format of a job, which they will not do out of the box without a custom adapter. Otherwise, port the UI concept onto Laravel's failed_jobs or Horizon data.
- What Laravel-native alternatives should I use instead of queue-manager-bundle?
- Use Laravel Horizon for Redis-backed queue visibility, Laravel Telescope for observability, and a thin internal admin screen over failed_jobs for retry and forget operations. Add policy gates and audit columns for destructive actions. These tools match Laravel's queue envelope and container semantics.
- Does queue-manager-bundle include authentication and authorization for its admin UI?
- Do not assume it does. The bundle's value is that operators can inspect payloads and requeue or delete jobs, which means an admin surface that renders potentially sensitive payloads and exposes destructive operations. Verify authentication, authorization granularity, and audit logging directly in the code before any commitment.
- Is mcfedr/queue-manager-bundle actively maintained and safe for production?
- It has a single maintainer, low stars and zero dependents, and a release dated 2024-09-25 that may be a maintenance heartbeat. Adoption risk includes bus factor and behavior drift if the underlying queue-manager abstraction lags broker versions. Confirm the maintainer's support posture and whether you are willing to own a fork.
- Which Symfony versions and dependencies does queue-manager-bundle require?
- It fits Symfony 5, 6, and 7 applications that already have symfony/framework-bundle and Twig configured. It integrates through Symfony's bundle registration, DI container, Configuration tree, and routing. Check the composer.json constraints for exact version support before installing.
- Which message brokers does queue-manager-bundle support?
- The underlying queue-manager library is broker-agnostic, with adapters for AMQP, Doctrine, and Redis-style queues. The bundle's headline use case is AMQP/RabbitMQ-style queues. This abstraction is architecturally reasonable but orthogonal to Laravel's queue drivers.