Weave Code
Rabbitmq Manager Bundle Laravel Package
myonlinestore/rabbitmq-manager-bundle
A web UI for managing RabbitMQ from your PHP application: browse queues, exchanges, and bindings; inspect, publish, and purge messages; and monitor broker health without leaving your admin panel.
rabbitmq-manager-bundle is a Symfony bundle that provides a lightweight service layer for interacting with RabbitMQ through its HTTP Management API. It lets you inspect and administer brokers from your application code or console commands, without dropping down to raw HTTP calls or shelling out to rabbitmqctl.
- Manage queues, exchanges, and bindings from a single injected service
- Inspect broker, node, and connection health and statistics
- Purge, delete, and declare resources programmatically
- Configure connection credentials and base URL via bundle configuration
- Integrates with Symfony's dependency injection and service container
Frequently asked questions about Rabbitmq Manager Bundle
- What does the myonlinestore/rabbitmq-manager-bundle do?
- It adds RabbitMQ management tooling to a Symfony app, letting you inspect queues, exchanges and bindings, publish and consume messages, and monitor broker activity from one interface. It is intended as lightweight admin tooling for PHP teams that want to stay inside the Symfony stack. It does not replace RabbitMQ's own management plugin; it gives you integrated views inside your app.
- How do I install rabbitmq-manager-bundle in Symfony?
- Install it with Composer using myonlinestore/rabbitmq-manager-bundle, then register the bundle in your Symfony application according to the README. You will also need a RabbitMQ broker and connection settings available to your app. Check the repository README for the exact registration and configuration steps for your Symfony version.
- Does this package work with Laravel?
- No, it is a Symfony bundle, not a Laravel package, so it does not ship a Laravel service provider or Laravel-specific configuration. Laravel teams evaluating it should expect Symfony bundle conventions and may need a different RabbitMQ admin solution. Treat this as Symfony-only tooling if you maintain both Symfony and Laravel apps.
- Which Symfony versions are supported?
- The repository's composer.json is the source of truth for supported Symfony and PHP versions. Check its require constraints and the README before installing in an older or newer Symfony app. If your Symfony version is outside the declared constraints, Composer will block installation or you may need an older release.
- Is rabbitmq-manager-bundle safe to use in production?
- Treat it as admin tooling and restrict access carefully, because it can expose queue contents, publish messages, and consume from queues. Put it behind authentication and authorization, and avoid enabling it on public-facing routes. Review the broker permissions you grant and test in staging before using it against production RabbitMQ.
- Can I publish and consume messages from the interface?
- Yes, the bundle's purpose is to let you publish and consume messages alongside inspecting queues, exchanges and bindings. Use test queues or staging brokers when trying payloads, because publishing and consuming can affect real consumers and message flow. Confirm behavior and permissions in the README before using it on production queues.
- How do I configure the RabbitMQ connection?
- The bundle needs broker connection details such as host, port, credentials, and vhost, typically supplied through Symfony configuration. The exact configuration keys and environment variable names should come from the package README rather than assumptions. Keep credentials out of version control and use Symfony secrets or environment variables.
- What are alternatives to rabbitmq-manager-bundle?
- RabbitMQ's own management plugin and web UI are the standard alternatives for inspecting queues, exchanges and bindings. Other PHP admin tools or custom Symfony controllers may fit if you need tighter integration. This bundle is a good fit when you want lightweight RabbitMQ management inside an existing Symfony admin area.
- How is the bundle maintained and updated?
- Maintenance activity, release history, and open issues are visible on the GitHub repository. Check the latest commit dates, tagged releases, and issue responses before adopting it for a long-lived project. Pin a compatible version in Composer and review changelogs when upgrading.
- How do I test rabbitmq-manager-bundle integration?
- Test against a disposable RabbitMQ instance or a containerized broker rather than production. Verify queue, exchange and binding views, then test publishing and consuming with non-critical messages. Keep the admin interface disabled or access-restricted in test and CI environments where it is not needed.
Weaver
How can I help you explore Laravel packages today?