RabbitMQ

A message broker for work that outlives the request that asked for it.

Your application connects as RABBITMQ_USER with RABBITMQ_PASSWORD, at RABBITMQ_HOST on port 5672, or with all of it in one RABBITMQ_URL. All four are in its environment. The password is made for each environment and never changes. The image's own guest account is removed.

RabbitMQ stops accepting messages when it reaches its memory limit. The limit is 60% of the queue machine when the broker has one to itself, and 60% of your plan when it shares a machine with your site. Set RABBITMQ_VM_MEMORY_HIGH_WATERMARK to use a different share, between 0.1 and 0.9.

Queues and messages are kept on disk, so a restart loses nothing a durable queue held.

#Versions

Pin the version, not the build: name 4.3.5 and the platform matches it to the current build, so a security rebuild reaches you without anybody editing a repository.

The version you name is the one your environment runs from the next deploy. This service keeps data, and not every version can read another's — before you change it, read Changing a service's version.

#What you can change

In vallic.yaml — what each one does is on Service settings:

services:
  - rabbitmq:
      version: '4.3.5'
      environment:
        RABBITMQ_VM_MEMORY_HIGH_WATERMARK: …

Anything not on this list refuses the deploy, naming the variable — rather than being accepted and quietly ignored.