rabbitmq-server/deps/rabbit/docs
Michael Klishin ec4f1dba7d
(c) year bump: 2022 => 2023
2023-01-01 23:17:36 -05:00
..
README-for-packages Change repo "root" to deps/rabbit 2020-11-13 14:34:42 +01:00
README.md Change repo "root" to deps/rabbit 2020-11-13 14:34:42 +01:00
advanced.config.example Change repo "root" to deps/rabbit 2020-11-13 14:34:42 +01:00
rabbitmq-diagnostics.8 (c) year bump: 2022 => 2023 2023-01-01 23:17:36 -05:00
rabbitmq-echopid.8 (c) year bump: 2022 => 2023 2023-01-01 23:17:36 -05:00
rabbitmq-env.conf.5 (c) year bump: 2022 => 2023 2023-01-01 23:17:36 -05:00
rabbitmq-plugins.8 (c) year bump: 2022 => 2023 2023-01-01 23:17:36 -05:00
rabbitmq-queues.8 (c) year bump: 2022 => 2023 2023-01-01 23:17:36 -05:00
rabbitmq-server.8 (c) year bump: 2022 => 2023 2023-01-01 23:17:36 -05:00
rabbitmq-server.service.example Add systemd hardening parameters in rabbitmq-server.service.example 2021-11-19 19:06:21 +08:00
rabbitmq-service.8 (c) year bump: 2022 => 2023 2023-01-01 23:17:36 -05:00
rabbitmq-streams.8 Add `rabbitmq-queues rebalance stream` to the man page 2022-12-19 10:50:40 +01:00
rabbitmq-upgrade.8 (c) year bump: 2022 => 2023 2023-01-01 23:17:36 -05:00
rabbitmq.conf.example Add a visible warning for mqtt.durable_queue_type 2022-04-05 14:34:32 +04:00
rabbitmqctl.8 (c) year bump: 2022 => 2023 2023-01-01 23:17:36 -05:00
set_rabbitmq_policy.sh.example Change repo "root" to deps/rabbit 2020-11-13 14:34:42 +01:00

README.md

Manual Pages and Documentation Extras

This directory contains CLI tool man page sources as well as a few documentation extras:

Please see rabbitmq.com for documentation guides.

Classic Config File Format Example

Feeling nostalgic and looking for the classic configuration file example? Now that's old school! Keep in mind that classic configuration file should be considered deprecated. Prefer rabbitmq.conf (see new style configuration format) with an advanced.config to complement it as needed.

man Pages

Source Files

This directory contains man pages that are are converted to HTML using mandoc:

gmake web-manpages

The result is then copied to the website repository

Contributions

Since deployed man pages are generated, it is important to keep them in sync with the source. Accepting community contributions — which will always come as website pull requests — is fine but the person who merges them is responsible for backporting all changes to the source pages in this repo.