Weave Code
Mq2Php Bundle Laravel Package
happyr/mq2php-bundle
Symfony bundle for bridging message queues to PHP consumers, simplifying queued message consumption and processing through configurable services and console commands.
Automatically consume messages from a message queue without using a cron. Works great with SimpleBus
Frequently asked questions about Mq2Php Bundle
- Is happyr/mq2php-bundle compatible with Laravel?
- No, not as a native integration. It is a Symfony bundle built around Symfony's bundle system, dependency-injection container, configuration tree, and console conventions, while Laravel uses a different container, queue abstraction, and Artisan lifecycle. Composer installation alone does not make it Laravel-compatible. Treat it as a reference implementation rather than a drop-in Laravel package.
- Can I install happyr/mq2php-bundle in a Laravel app with Composer?
- You can attempt a Composer install, but that does not create a supported Laravel integration. The package expects Symfony bundle wiring and may pull stale Symfony or PHP constraints that conflict with modern Laravel applications. Booting the Symfony bundle inside Laravel is not a viable production path without a Symfony bridge and significant engineering ownership. Use a time-boxed spike only if you need to inspect the code.
- What does happyr/mq2php-bundle actually do?
- It integrates the mq2php consumer library into Symfony so AMQP brokers such as RabbitMQ can deliver messages to ordinary PHP services. Queues, consumers, and connection settings are declared in bundle configuration, and consumers are registered as tagged services that a long-running worker can execute. It also provides a Symfony console command for starting and managing workers, with pluggable message handlers and logging support.
- How do I install and configure happyr/mq2php-bundle?
- In a Symfony application you would add the package with Composer, enable the bundle, and define connections, queues, and consumers in bundle configuration. Each consumer would be wired as a tagged service and run through the bundle's console command. In Laravel this configuration model does not map directly to config files or Artisan, so you would need an adapter rather than standard installation steps.
- Does happyr/mq2php-bundle support Laravel 10 or PHP 8?
- Compatibility with Laravel 10 or PHP 8 is not established and should be treated as unknown or likely broken. The last release was 2018-01-29, which predates modern Laravel and PHP releases, and the package has minimal adoption. Validate PHP, Symfony component, broker client extension, and Composer dependency constraints in a spike before relying on it.
- How do I run MQ2PHP consumers as a Laravel worker or Artisan command?
- There is no native Artisan worker for this Symfony bundle. A realistic approach is to fork or extract the core message-handling logic, wrap it in a Laravel service provider, and expose it through a custom Artisan command or queue worker. Alternatively, implement the same behavior with Laravel jobs, queue workers, retries, and failed-job handling.
- What are the Laravel alternatives to happyr/mq2php-bundle for RabbitMQ?
- Laravel's native queue system supports jobs, workers, retries, failed-job storage, and observability, and can be paired with maintained RabbitMQ broker packages. If you use Redis, Horizon adds monitoring and management for Laravel queues. For mandatory MQ2PHP protocols, build a small adapter around extracted logic rather than adopting the Symfony bundle directly.
- Can I extract the message-handling logic from happyr/mq2php-bundle into a Laravel service provider?
- Possibly, but it requires a fork and a careful audit because the package is old, minimally adopted, and likely tied to Symfony wiring. The core broker and message-handling code may be separable from bundle configuration and tagged-service registration. You would still need to own compatibility, security patching, CI, and the upgrade path.
- Is happyr/mq2php-bundle maintained and safe for production?
- It should not be adopted as a production dependency by default. The last release was 2018-01-29, it has 1 star, 0 dependents, and a score of 0.065, which signals minimal adoption and likely stale compatibility constraints. Production use would require a fork, dependency audit, ownership plan, and explicit handling of security and maintenance risk.
- What should I check before forking happyr/mq2php-bundle for Laravel?
- Document the exact MQ2PHP behavior and message contract, including broker protocol, retry semantics, dead-letter behavior, and idempotency requirements. Confirm whether Laravel's native queues and maintained broker packages can meet the need before forking. If you proceed, audit PHP 8.x and current Laravel compatibility, isolate broker logic behind Laravel contracts, and assign ownership for security patching, CI, and upgrades.
Weaver
How can I help you explore Laravel packages today?