rabbitmq-server/deps/rabbit/docs
Luke Bakken 040a4b7e39
Remove weird characters
Fixes #10767
2024-03-18 10:00:58 -07:00
..
README-for-packages
README.md remove repetitive words (#8981) 2023-07-31 12:50:52 +02:00
advanced.config.example
rabbitmq-diagnostics.8 Update (c) according to [1] 2023-11-21 23:18:22 -05:00
rabbitmq-echopid.8 Update (c) according to [1] 2023-11-21 23:18:22 -05:00
rabbitmq-env.conf.5 Update (c) according to [1] 2023-11-21 23:18:22 -05:00
rabbitmq-plugins.8 Update (c) according to [1] 2023-11-21 23:18:22 -05:00
rabbitmq-queues.8 Update (c) according to [1] 2023-11-21 23:18:22 -05:00
rabbitmq-server.8 Update (c) according to [1] 2023-11-21 23:18:22 -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 Update (c) according to [1] 2023-11-21 23:18:22 -05:00
rabbitmq-streams.8 rabbitmq-streams(8) wording 2024-02-07 08:01:26 -05:00
rabbitmq-upgrade.8 Update (c) according to [1] 2023-11-21 23:18:22 -05:00
rabbitmq.conf.example Remove weird characters 2024-03-18 10:00:58 -07:00
rabbitmqctl.8 Remove rabbitmqctl(8) entry of (now a no-op) rename_cluster_node and friends 2024-01-19 11:22:16 -05:00
set_rabbitmq_policy.sh.example

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 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.