1RABBITMQ-ENV.CONF(5) RabbitMQ Server RABBITMQ-ENV.CONF(5)
2
3
4
6 rabbitmq-env.conf - default settings for RabbitMQ AMQP server
7
9 /etc/rabbitmq/rabbitmq-env.conf contains variable settings that
10 override the defaults built in to the RabbitMQ startup scripts.
11
12 The file is interpreted by the system shell, and so should consist of a
13 sequence of shell environment variable definitions. Normal shell syntax
14 is permitted (since the file is sourced using the shell "." operator),
15 including line comments starting with "#".
16
17 In order of preference, the startup scripts get their values from the
18 environment, from /etc/rabbitmq/rabbitmq-env.conf and finally from the
19 built-in default values. For example, for the RABBITMQ_NODENAME
20 setting,
21
22 RABBITMQ_NODENAME
23
24 from the environment is checked first. If it is absent or equal to the
25 empty string, then
26
27 NODENAME
28
29 from /etc/rabbitmq/rabbitmq-env.conf is checked. If it is also absent
30 or set equal to the empty string then the default value from the
31 startup script is used.
32
33 The variable names in /etc/rabbitmq/rabbitmq-env.conf are always equal
34 to the environment variable names, with the RABBITMQ_ prefix removed:
35 RABBITMQ_NODE_PORT from the environment becomes NODE_PORT in the
36 /etc/rabbitmq/rabbitmq-env.conf file, etc.
37
38 For example:
39
40 # I am a complete /etc/rabbitmq/rabbitmq-env.conf file.
41 # Comment lines start with a hash character.
42 # This is a /bin/sh script file - use ordinary envt var syntax
43 NODENAME=hare
44
45
46 This is an example of a complete /etc/rabbitmq/rabbitmq-env.conf file
47 that overrides the default Erlang node name from "rabbit" to "hare".
48
50 rabbitmq-server(1) rabbitmqctl(1)
51
53 The RabbitMQ Team <<info@rabbitmq.com>>
54
55
56
57RabbitMQ Server 07/20/2018 RABBITMQ-ENV.CONF(5)