Skip to content

Commit 8e83a56

Browse files
committed
Add some notes in rabbitmq about "RABBITMQ_SERVER_ADDITIONAL_ERL_ARGS"
1 parent 7b30b0f commit 8e83a56

File tree

1 file changed

+11
-3
lines changed

1 file changed

+11
-3
lines changed

rabbitmq/content.md

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@ $ docker run -d --hostname my-rabbit --name some-rabbit -p 8080:15672 rabbitmq:3
8888

8989
You can then go to `http://localhost:8080` or `http://host-ip:8080` in a browser.
9090

91-
## Setting default user and password
91+
### Setting default user and password
9292

9393
If you wish to change the default username and password of `guest` / `guest`, you can do so with the `RABBITMQ_DEFAULT_USER` and `RABBITMQ_DEFAULT_PASS` environmental variables:
9494

@@ -98,15 +98,15 @@ $ docker run -d --hostname my-rabbit --name some-rabbit -e RABBITMQ_DEFAULT_USER
9898

9999
You can then go to `http://localhost:8080` or `http://host-ip:8080` in a browser and use `user`/`password` to gain access to the management console
100100

101-
## Setting default vhost
101+
### Setting default vhost
102102

103103
If you wish to change the default vhost, you can do so with the `RABBITMQ_DEFAULT_VHOST` environmental variables:
104104

105105
```console
106106
$ docker run -d --hostname my-rabbit --name some-rabbit -e RABBITMQ_DEFAULT_VHOST=my_vhost rabbitmq:3-management
107107
```
108108

109-
## Enabling HiPE
109+
### Enabling HiPE
110110

111111
**Warning:** if you're using the Alpine variant, there is currently [an outstanding bug (Alpine Linux bug #5700) with the `erlang-hipe` package](https://bugs.alpinelinux.org/issues/5700) which prevents HiPE from working in Alpine Linux. See [docker-library/rabbitmq#151](https://github.com/docker-library/rabbitmq/issues/151) for more discussion.
112112

@@ -118,6 +118,14 @@ For enabling the HiPE compiler on startup use `RABBITMQ_HIPE_COMPILE` set to `1`
118118
119119
It is therefore important to take that startup delay into consideration when configuring health checks, automated clustering etc.
120120

121+
### Additional Configuration
122+
123+
If additional configuration is required, it is recommended to use the `RABBITMQ_SERVER_ADDITIONAL_ERL_ARGS` environment variable, whose syntax is described [in section 7.8 ("Configuring an Application") of the Erlang OTP Design Principles User's Guide](http://erlang.org/doc/design_principles/applications.html#id81887) (the appropriate value for `-ApplName` is `-rabbit`).
124+
125+
For example, configuring [`log_levels`](https://www.rabbitmq.com/configure.html#config-items) would look something like `-e RABBITMQ_SERVER_ADDITIONAL_ERL_ARGS="-rabbit log_levels [{connection,error}]"`.
126+
127+
Additional configuration keys would be specified as a list. For example, configuring both [`log_levels`](https://www.rabbitmq.com/configure.html#config-items) and [`auth_backends`](https://www.rabbitmq.com/ldap.html#overview) would look something like `-e RABBITMQ_SERVER_ADDITIONAL_ERL_ARGS="-rabbit log_levels [{connection,error}] auth_backends [rabbit_auth_backend_ldap]"`.
128+
121129
## Connecting to the daemon
122130

123131
```console

0 commit comments

Comments
 (0)