- Is phobetor/rabbitmq-supervisor-bundle compatible with Laravel?
- No. phobetor/rabbitmq-supervisor-bundle is a Symfony bundle, not a Laravel package, and the technical evaluation rates Laravel fit as weak-to-absent. Laravel applications should use Horizon or a hand-rolled Supervisor config instead. It could only be reused as a standalone Supervisor config template with config bootstrapped outside Symfony's kernel.
- How do I install phobetor/rabbitmq-supervisor-bundle?
- Install it with Composer, register the bundle in your Symfony kernel, and define your RabbitMQ consumer daemons in configuration. Then generate the Supervisor programs and run supervisorctl reread and update to apply them. Version 3.3.0 derives paths from kernel.project_dir when available, so deploy-time path drift is less likely.
- What Symfony and PHP versions does version 3.3.0 support?
- The provided context does not include a published support matrix for 3.3.0. It highlights kernel.project_dir handling for Symfony 3+ projects and notes no deprecations or removals in the minor release. Check the package's composer.json constraints and README before committing to a Symfony or PHP version.
- What changed in 3.3.0 that could affect my deployment pipeline?
- Version 3.3.0 changes three behaviors: it waits for supervisord by default, groups consumers so supervisor sends signals in parallel, and uses kernel.project_dir when available. The wait default is the item most likely to surface in CI and deploy pipelines. Parallel group signaling changes shutdown from a staggered drain to a synchronized one, which can cause reconnect storms.
- Does this bundle manage RabbitMQ connections or just Supervisor configs?
- It does not broker RabbitMQ connections itself; it generates Supervisor program blocks and issues start and stop commands. The actual connections come from php-amqplib or a Symfony Messenger transport. Adoption is therefore a configuration and process-supervision exercise rather than a code-integration one.
- Are consumer signals sent in parallel in 3.3.0, and what are the risks?
- Yes. In 3.3.0 consumers are grouped so supervisor fans signals out in parallel instead of serially. That shortens restart time but converts a staggered drain into a synchronized one, with consequences for queue reconnect storms and in-flight message handling. Consumers should be idempotent and tolerant of abrupt SIGTERM, and you should check your maximum simultaneous-consumer count against RabbitMQ connection and channel limits.
- Is there an opt-out flag for waiting for supervisord in 3.3.0?
- The evaluation flags wait-for-supervisord by default as a behavior risk but does not name an opt-out flag. You need to check the README and diff the 3.2.2 versus 3.3.0 configuration for the exact option and default. Until confirmed, assume control commands will block or fail fast when supervisord is unavailable.
- How should I test Supervisor config generation in CI?
- Capture supervisorctl output or the generated .conf files before and after the upgrade and diff them. That diff is the critical review step, especially for the new wait-for-supervisord default and grouped programs. Pin the Composer version so config generation stays deterministic in CI.
- Is phobetor/rabbitmq-supervisor-bundle actively maintained?
- It is a low-activity, effectively single-maintainer package, so bus factor is the dominant long-term risk. The 3.3.0 release signals no deprecations or removals, but release cadence and maintainer count are unclear from the context. Pin versions and keep a fallback Supervisor template in case maintenance stalls.
- What are the alternatives to this bundle for Laravel or Symfony?
- For Laravel, use Horizon or a hand-rolled Supervisor configuration instead of this bundle. For Symfony 3+ with php-amqplib or Symfony Messenger consumers, the bundle fits cleanly as a process-definition layer. On mixed estates, treat it as a Supervisor-config artifact producer and keep it out of the request-serving application's dependency graph.