Download the PHP package phobetor/rabbitmq-supervisor-bundle without Composer
On this page you can find all versions of the php package phobetor/rabbitmq-supervisor-bundle. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download phobetor/rabbitmq-supervisor-bundle
More information about phobetor/rabbitmq-supervisor-bundle
Files in phobetor/rabbitmq-supervisor-bundle
Package rabbitmq-supervisor-bundle
Short Description Symfony bundle to automatically create and update supervisor configurations for RabbitMQ consumer daemons
License MIT
Homepage https://github.com/Phobetor/rabbitmq-supervisor-bundle
Informations about the package rabbitmq-supervisor-bundle
RabbitMQ supervisor bundle
Symfony bundle to automatically create and update supervisor configurations for php-amqplib/rabbitmq-bundle
(and its predecessor oldsound/rabbitmq-bundle
) RabbitMQ consumer daemons.
In a nutshell | tl;dr
If you use php-amqplib/rabbitmq-bundle
to handle the communication with RabbitMQ, just install supervisor, add this bundle and run
to get a running supervisord
instance that automatically manages all your consumer daemons.
When your worker configuration or your code changes, run the command again and all the daemons will be updated.
Installation
Install supervisor. e. g. on debian based distributions via apt-get
:
Add bundle via composer
This will install the bundle to your project’s vendor
directory.
If your are not using Symfony Flex, also add the bundle to your project’s AppKernel
:
Symfony 5:
Zero Configuration
RabbitMQ supervisor bundle works out of the box with a predefined configuration. If you leave it this way you will end up with this directory structure:
In symfony 2 and 3 this will be placed inside your app/
directory.
Caution with symfony 4: to not have this inside of your src/
directory you need to set the paths to suit your needs.
E. g. to use the standard structure inside of the var/
directory, use this:
Advanced configuration
To see all configuration options run
BC break when updating from v1. to v2.
If you used custom commands before version 2.0, you need to update them. In most case you can just remove everything after the command name.
BC break when updating from v2. to v3.
Commands will by default no longer wait for supervisord
to complete. If you need this (e. g. to get feedback on
errors) use the --wait-for-supervisord
option.
Usage
Build or rebuild the supervisor and worker configuration and start the daemon:
Control the supervisord daemon:
All versions of rabbitmq-supervisor-bundle with dependencies
symfony/console Version ~2.5|~3.0|~4.0|~5.0
symfony/process Version ~2.5|~3.0|~4.0|~5.0