'\" t
.\"     Title: rabbitmq-env.conf
.\"    Author: The RabbitMQ Team <\m[blue]\fB<info@rabbitmq.com>\fR\m[]>
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
.\"      Date: 01/11/2017
.\"    Manual: RabbitMQ Server
.\"    Source: RabbitMQ Server
.\"  Language: English
.\"
.TH "RABBITMQ\-ENV\&.CONF" "5" "01/11/2017" "RabbitMQ Server" "RabbitMQ Server"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.\" http://bugs.debian.org/507673
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\" -----------------------------------------------------------------
.\" * set default formatting
.\" -----------------------------------------------------------------
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
.SH "NAME"
rabbitmq-env.conf \- default settings for RabbitMQ AMQP server
.SH "DESCRIPTION"
.PP
/etc/rabbitmq/rabbitmq\-env\&.conf
contains variable settings that override the defaults built in to the RabbitMQ startup scripts\&.
.PP
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 "#"\&.
.PP
In order of preference, the startup scripts get their values from the environment, from
/etc/rabbitmq/rabbitmq\-env\&.conf
and finally from the built\-in default values\&. For example, for the
\fBRABBITMQ_NODENAME\fR
setting,
.PP
\fBRABBITMQ_NODENAME\fR
.PP
from the environment is checked first\&. If it is absent or equal to the empty string, then
.PP
\fBNODENAME\fR
.PP
from
/etc/rabbitmq/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\&.
.PP
The variable names in /etc/rabbitmq/rabbitmq\-env\&.conf are always equal to the environment variable names, with the
\fBRABBITMQ_\fR
prefix removed:
\fBRABBITMQ_NODE_PORT\fR
from the environment becomes
\fBNODE_PORT\fR
in the
/etc/rabbitmq/rabbitmq\-env\&.conf
file, etc\&.
.sp
.nf
# I am a complete /etc/rabbitmq/rabbitmq\-env\&.conf file\&.
# Comment lines start with a hash character\&.
# This is a /bin/sh script file \- use ordinary envt var syntax
NODENAME=hare
        
.fi
.SH "SEE ALSO"
.PP
\fBrabbitmq-server\fR(1)\fBrabbitmqctl\fR(1)
.SH "EXAMPLES"
.sp
.nf
      \fB
# I am a complete /etc/rabbitmq/rabbitmq\-env\&.conf file\&.
# Comment lines start with a hash character\&.
# This is a /bin/sh script file \- use ordinary envt var syntax
NODENAME=hare
        \fR
    
.fi
.PP
This is an example of a complete
/etc/rabbitmq/rabbitmq\-env\&.conf
file that overrides the default Erlang node name from "rabbit" to "hare"\&.
.SH "AUTHOR"
.PP
\fBThe RabbitMQ Team <\fR\fB\m[blue]\fB<info@rabbitmq\&.com>\fR\m[]\fR\fB>\fR