https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417 --- Comment #61 from David Cook <dcook@prosentient.com.au> --- (In reply to Tomás Cohen Arazi from comment #59)
As discussed by other means, my only concerns are: - should we make it opt-in at this stage (i.e. keep the current scripts, but have a config/syspref that defines if the rabbitmq + daemon should be used). As it is packaged in the supported distros/versions it is not *that* important but worth discussing.
With my local experiments, I've made it opt-in, so that I can manually switch over and evaluate whether my approach to the message queue is working well enough. I check to see if the "Net::Stomp" module is available and if the koha-conf.xml file has the configuration I need. That works well.
- I don't agree with pulling the rabbitmq-server package automatically on a Debian install. We don't do that with mysql-server/mariadb-server and we should follow that approach. i.e. on the install notes, there will be an entry, before installing koha-common, which will say 'RabbitMQ' and will explain that if you already have one running, you point to it when calling koha-create (bug 25674) and otherwise what command to run for installing it.
I agree. While we've decided to run rabbitmq-server locally on each server, it is a reasonable choice to use external RabbitMQ servers. -- You are receiving this mail because: You are watching all bug changes.