Add RabbitMQ as recommended system-requirement

[skoch98]

As discussed with Bernhard Rusch at the Inspire, I am now adding RabbitMQ as a recommended system requirement in the documentation. I tried to present RabbitMQ's arguments as convincingly as possible... 😄

[github-actions]

Review Checklist

• Target branch (11.2 for bug fixes, others 11.x)
• Tests (if it's testable code, there should be a test for it - get help)
• Docs (every functionality needs to be documented, see here)
• Migration incl. install.sql (e.g. if the database schema changes, ...)
• Upgrade notes (deprecations, important information, migration hints, ...)
• Label
• Milestone

[brusch]

LGTM, I think we should also include an example of how to configure RabbitMQ, that would make it more convenient for users 😊

[skoch-twocream]

LGTM, I think we should also include an example of how to configure RabbitMQ, that would make it more convenient for users 😊

I would use this scheme as an example:

• https://github.com/pimcore/skeleton/blob/fbd28ac2b65fe81bb69b581c94191e80bce18a88/.docker/messenger.yaml

This way there is an .ENV varaible for the base DSN and it is possible to use multiple queues.

Alternatively, I can document it in a simplified way so that the .ENV contains the queue directly and therefore all tasks run into it (I find it not recommend but possibly easier and more error-free to understand for the usual user).

[brusch]

For me it would be fine that we just reference to the skeleton file.
So I'd then finish pimcore/skeleton#187 first and then update this PR.

[brusch]

Btw. just released v3.2 of our docker image with AMQP support ... just building at the moment:
https://github.com/pimcore/docker/actions/runs/8520253593

[fashxp]

can we also make that statement consistent: https://github.com/pimcore/pimcore/blob/11.x/doc/01_Getting_Started/02_Advanced_Installation_Topics/01_Symfony_Messenger.md?plain=1#L22

[skoch98]

can we also make that statement consistent: https://github.com/pimcore/pimcore/blob/11.x/doc/01_Getting_Started/02_Advanced_Installation_Topics/01_Symfony_Messenger.md?plain=1#L22

For pimcore_core sure. But personally, I would leave the failed queue in the database so that it is easier to view it and report it if there are errors. What is your vendor view on this?

[brusch]

@skoch98 yes, I'd leave failed queue in db as well 👍

[skoch98]

I updated the docs but please make sure that pimcore/skeleton#187 will merged first so that the link is valid :-)

Edit: I think this is better for everyone: 4803044

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[mcop1]

Since pimcore/docker#152 was merged, the image was released and the pr looks good, I merged it.
Thanks everyone for creating/improving the pr 👍