Go to main content

man pages section 5: File Formats

Exit Print View

Updated: Thursday, June 13, 2019

rabbitmq-env.conf (5)


rabbitmq-env.conf - default settings for RabbitMQ AMQP server


Please see following description for synopsis


RABBITMQ-ENV.CONF(5)        BSD File Formats Manual       RABBITMQ-ENV.CONF(5)

     rabbitmq-env.conf -- default settings for RabbitMQ AMQP server

     rabbitmq-env.conf contains variable settings that override the defaults
     built in to the RabbitMQ startup scripts.

     The file is interpreted by the system shell, and so should consist of a
     sequence of shell environment variable definitions.  Normal shell syntax
     is permitted (since the file is sourced using the shell "." operator),
     including line comments starting with "#".

     In order of preference, the startup scripts get their values from the
     environment, from rabbitmq-env.conf and finally from the built-in default
     values.  For example, for the RABBITMQ_NODENAME setting,
     RABBITMQ_NODENAME from the environment is checked first.  If it is absent
     or equal to the empty string, then NODENAME from rabbitmq-env.conf is
     checked.  If it is also absent or set equal to the empty string then the
     default value from the startup script is used.

     The variable names in rabbitmq-env.conf are always equal to the environ-
     ment variable names, with the "RABBITMQ_" prefix removed:
     RABBITMQ_NODE_PORT from the environment becomes NODE_PORT in
     rabbitmq-env.conf, etc.

     Here is an example of a complete rabbitmq-env.conf file that overrides
     the default Erlang node name from "rabbit" to "hare".

           # I am a complete rabbitmq-env.conf file.
           # Comment lines start with a hash character.
           # This is a /bin/sh script file - use ordinary envt var syntax

     rabbitmq-plugins(8), rabbitmq-server(8), rabbitmqctl(8)

     The RabbitMQ Team <info@rabbitmq.com>

RabbitMQ Server                 April 25, 2017                 RabbitMQ Server