How To Upload A File To Rabbitmq Config

How to configure RabbitMQ properly

In a project I'yard involved in, we started using RabbitMQ to support internal communication betwixt different microservices. At the beginning nosotros have been using rabbitmqadmin to create all the queues at startup — this isn't a production ready solution. Let's read how you should configure RabbitMQ to fully control who changed what.

Every bit I mentioned nosotros started with a simple instance, right at present we are extending the usage of RabbitMQ and adding support for collecting all information and events happening in different parts of our system. We decided to use an substitution of type fanout and a few dedicated queues that receive events.

The whole configuration was done via a batch file using rabbitmqctl and rabbitmqadmin. And yes, we are using Docker to configure all our services. Beneath is our current Dockerfile before I have introduced configuration via files:

Erstwhile Dockerfile

There is a one huge drawback when you want to use those tools — a RabbitMQ server must be up & running, without this you won't be able to connect to the server and configure anything.

To overcome this effect we simple used aslumber command to await a bit when RabbitMQ volition be ready.

Configuring RabbitMQ via a batch file — run.sh

As you meet this is a good thought if yous want to play with RabbitMQ, but a totally bad thought when you desire to run RabbitMQ in production.

Configuration files

RabbitMQ supports few options if you want to configure it via files. First at that place is a rabbitmq.conf file located in /etc/rabbitmq — it uses a new format available since RabbitMQ 3.7. If you want to utilise an old format, proper noun your file rabbitmq.config and you can utilise an Erlang term configuration format instead.

A good idea is to start with an example config file published on Github. Yous tin read throughout it and uncomment and change options you want.

If you need to configure some avant-garde feature, it's a skillful thought to employ another file — advanced.conf.

Also plugins allow you lot to utilise config files, e.g. if you want to use the Direction Plugin (a Rest API along with a Web UI) and configure information technology via a file, you can define proper options in rabbitmq.conf, as specified on the plugin page.

You can also use the Management Plugin to configure queues, exchanges and policies based on a JSON file. This is the super like shooting fish in a barrel pick if you want to accept a version controlled configuration. All you take to do is to tell the plugin to load the configuration from the JSON file:

direction.load_definitions = /etc/rabbitmq/definitions.json

Add together the above line to your rabbitmq.conf file as specified on the plugin folio and you are washed.

Y'all volition probably ask how to prepare the definitions.json file? The easies, and the most convenient way is to use the Direction Plugin UI interface to setup everything you demand and export the whole configuration into the file.

On the Overview folio of the UI, at the bottom, you lot volition find a push button Download broker definitions that will export the whole configuration of the RabbitMQ into a JSON file. Only use the file with new options in your Dockerfile as presented beneath:

Terminal Dockerfile

Summary

Using cli tools is good if you lot want to setup RabbitMQ fast and your setup isn't too complicated. If there are more options and you want to control what and when was changed by who, using configuration files is a far better solution.