Infrastructure/infra-docs-fpo
3
0
Fork 0
Code Issues 100 Pull requests 6 Projects Releases Packages Wiki Activity Actions

Update the developer guide

Browse source 
This commit is fixing all non-functional links and updates the content to more up to date state.

It also removes fedmsg from the guide.

Signed-off-by: Michal Konečný <mkonecny@redhat.com>
This commit is contained in:
Michal Konečný 2022-04-14 17:29:46 +02:00
parent 50d59f41df
commit 6bd7ef5065
13 changed files with 164 additions and 220 deletions
Download patch file Download diff file Expand all files Collapse all files

5
modules/developer_guide/pages/messaging.adoc
View file

@ -7,7 +7,7 @@ by an AMQP message broker and the
https://fedora-messaging.readthedocs.io/en/latest/[fedora-messaging] for
Python applications. This documentation outlines the policies for
sending and receiving messages. To learn how to send and receive
messages, see the fedora-messaging documentation.
messages, see the https://fedora-messaging.readthedocs.io/en/latest[fedora-messaging documentation].
=== Broker URLs
@ -16,7 +16,7 @@ through the proxies at `amqps://rabbitmq.fedoraproject.org` for
production and `amqps://rabbitmq.stg.fedoraproject.org` for staging.
Clients can connect using these URLs both inside and outside the Fedora
VPN, but users outside need to use a separate virtual host. Consult the
https://fedora-messaging.readthedocs.io/en/stable/fedora-broker.html[fedora-messaging
https://fedora-messaging.readthedocs.io/en/latest/quick-start.html#fedora-s-public-broker[fedora-messaging
documentation] for details on how to connect externally.
=== Identity
@ -61,7 +61,6 @@ configuration so that if they do not exist, the application will fail
with a helpful error message about which resource is not available.
[WARNING]
.Warning
====
Because AMQP clients don't have permission to create objects, you need
to set