mirror of
https://github.com/parkervcp/eggs.git
synced 2024-11-23 04:52:52 +08:00
fixed heading levels
added blank lines as needed removed trailing spaces
This commit is contained in:
parent
6753290356
commit
268e90adba
@ -1,32 +1,36 @@
|
|||||||
# RabbitMQ
|
# RabbitMQ
|
||||||
|
|
||||||
### From the [RabbitMQ](https://www.rabbitmq.com/) website
|
## From the [RabbitMQ](https://www.rabbitmq.com/) website
|
||||||
|
|
||||||
RabbitMQ is the most widely deployed open source message broker.
|
RabbitMQ is the most widely deployed open source message broker.
|
||||||
|
|
||||||
### Installation
|
## Installation
|
||||||
|
|
||||||
Follow the common egg installation guide to install the egg on your Pterodactyl instance.
|
Follow the common egg installation guide to install the egg on your Pterodactyl instance.
|
||||||
When setting up a server, the latest RabbitMQ version will be used by default.
|
When setting up a server, the latest RabbitMQ version will be used by default.
|
||||||
|
|
||||||
With pretty new and old versions of RabbitMQ, you might have to adjust the used Erlang version.
|
With pretty new and old versions of RabbitMQ, you might have to adjust the used Erlang version.
|
||||||
This can be archived by adjusting the version number of the used image (e. g. `ghcr.io/pterodactyl/yolks:erlang_22` instead of `ghcr.io/parkervcp/yolks:erlang_24`).
|
This can be archived by adjusting the version number of the used image (e. g. `ghcr.io/pterodactyl/yolks:erlang_22` instead of `ghcr.io/parkervcp/yolks:erlang_24`).
|
||||||
|
|
||||||
### Configuration
|
## Configuration
|
||||||
|
|
||||||
Configuring RabbitMQ in Pterodactyl is only possible using the config files.
|
Configuring RabbitMQ in Pterodactyl is only possible using the config files.
|
||||||
This means:
|
This means:
|
||||||
|
|
||||||
- Configure the server itself as normal using `/home/container/etc/rabbitmq/rabbitmq.conf`
|
- Configure the server itself as normal using `/home/container/etc/rabbitmq/rabbitmq.conf`
|
||||||
- Enable plugins using the plugin file located at `/home/container/etc/rabbitmq/enabled_plugins`
|
- Enable plugins using the plugin file located at `/home/container/etc/rabbitmq/enabled_plugins`
|
||||||
- Configure users and vhosts through a [definitions.json](https://www.rabbitmq.com/definitions.html)
|
- Configure users and vhosts through a [definitions.json](https://www.rabbitmq.com/definitions.html)
|
||||||
|
|
||||||
You can set the path to the used `definitions.json` using the `load_definitions` option in your config.
|
You can set the path to the used `definitions.json` using the `load_definitions` option in your config.
|
||||||
Note that RabbitMQ versions prior to 3.8.6 will require a properly configured management plugin to do so!
|
Note that RabbitMQ versions prior to 3.8.6 will require a properly configured management plugin to do so!
|
||||||
The easiest way to get a working `definitions.json` is to setup a local instance with the
|
The easiest way to get a working `definitions.json` is to setup a local instance with the management plugin. You can configure your instance there and load the definitions as stated by uploading them.
|
||||||
management plugin. You can configure your instance there and load the definitions as stated by uploading them.
|
|
||||||
|
|
||||||
By default, only `listeners.tcp.default` is configured to match your primary allocation.
|
By default, only `listeners.tcp.default` is configured to match your primary allocation.
|
||||||
If you want to expose some other port (e. g. the web management interface) you have to manually configure the
|
If you want to expose some other port (e. g. the web management interface) you have to manually configure the
|
||||||
port in your `rabbitmq.conf`.
|
port in your `rabbitmq.conf`.
|
||||||
|
|
||||||
### Update support
|
## Update support
|
||||||
|
|
||||||
The egg _should_ keep the `etc` folder when reinstalling, to prevent destroying the configuration by accident. Therefore a reinstallation with "latest" as the selected version can be used to update RabbitMQ.
|
The egg _should_ keep the `etc` folder when reinstalling, to prevent destroying the configuration by accident. Therefore a reinstallation with "latest" as the selected version can be used to update RabbitMQ.
|
||||||
|
|
||||||
If you want to reset the server completly, remove the `etc` directory manually before reinstalling.
|
If you want to reset the server completly, remove the `etc` directory manually before reinstalling.
|
||||||
|
Loading…
Reference in New Issue
Block a user