Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update documentation to reflect RabbitMQ developments #181

Open
rjgildea opened this issue May 17, 2022 · 1 comment
Open

Update documentation to reflect RabbitMQ developments #181

rjgildea opened this issue May 17, 2022 · 1 comment

Comments

@rjgildea
Copy link
Contributor

In particular, the Getting Started page should emphasise using RabbitMQ in preference to ActiveMQ.

@dsclassen
Copy link

Would it be possible to add the rabbitmq_config.yaml file that is needed by zocalo.configure_rabbitmq?

As it currently stands I am manually adding queues when I get an error while starting a Zocalo service. However, when I manually create the queues I don't know if I am applying the proper settings. For example I got errors indicating that filewatcher or processing_recipes queue where missing so I manually made them as Classic/Durable queues. There are many options for queues, and maybe they need certain properties?... see this screen shot from the RabbitMQ admin panel:

Screen Shot 2022-09-23 at 6 23 35 PM

ndevenish added a commit that referenced this issue Sep 6, 2023
This is (at time of commit) the current rabbitmq configuration being applied
at Diamond, and an example of the folder to use for user generation.

Addresses request in #181.
ndevenish added a commit that referenced this issue Sep 6, 2023
This is (at time of commit) the current rabbitmq configuration being applied
at Diamond, and an example of the folder to use for user generation.

Addresses request in #181.
ndevenish added a commit that referenced this issue Jul 19, 2024
This is (at time of commit) the current rabbitmq configuration being applied
at Diamond, and an example of the folder to use for user generation.

Addresses request in #181.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants