rabbitmq-server/deps/rabbit/docs
Michael Klishin f7d32d69f8 Introduce a new CLI tool (scope), rabbitmq-tanzu
For Tanzu (commercial) plugins to attach their commands to instead of
polluting rabbitmqctl.

Pair: @pjk25
(cherry picked from commit 6e0f2436fa)
2021-11-30 14:54:09 +00:00
..
README-for-packages
README.md
advanced.config.example
rabbitmq-diagnostics.8 Introduce a new CLI tool (scope), rabbitmq-tanzu 2021-11-30 14:54:09 +00:00
rabbitmq-echopid.8 Introduce a new CLI tool (scope), rabbitmq-tanzu 2021-11-30 14:54:09 +00:00
rabbitmq-env.conf.5 Introduce a new CLI tool (scope), rabbitmq-tanzu 2021-11-30 14:54:09 +00:00
rabbitmq-plugins.8 Introduce a new CLI tool (scope), rabbitmq-tanzu 2021-11-30 14:54:09 +00:00
rabbitmq-queues.8 Introduce a new CLI tool (scope), rabbitmq-tanzu 2021-11-30 14:54:09 +00:00
rabbitmq-server.8 Introduce a new CLI tool (scope), rabbitmq-tanzu 2021-11-30 14:54:09 +00:00
rabbitmq-server.service.example
rabbitmq-service.8 Introduce a new CLI tool (scope), rabbitmq-tanzu 2021-11-30 14:54:09 +00:00
rabbitmq-upgrade.8 Introduce a new CLI tool (scope), rabbitmq-tanzu 2021-11-30 14:54:09 +00:00
rabbitmq.conf.example
rabbitmqctl.8 Introduce a new CLI tool (scope), rabbitmq-tanzu 2021-11-30 14:54:09 +00: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 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.