https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417
--- Comment #237 from David Cook <[email protected]> --- (In reply to Jonathan Druart from comment #236) > I have 2 questions: > > We need > apt install rabbitmq-server > rabbitmq-plugins enable rabbitmq_stomp > service rabbitmq-server restart > > we can have rabbitmq-server inside control.in, but what about the 2 other > commands? > > Should we have them part of the install process or in koha-common (like we > try to guess if the plugin is enabled, otherwise we enable it and restart > rabbitmq)? > I think that we should probably treat rabbitmq setup the same way we treat mysql installation; that is, as a separate step. The Koha server(s) should only be concerned with the network connection to RabbitMQ. The sysadmin should be responsible for configuring RabbitMQ apart from that. (Same day, we might change our mind about that, in that case I'd say probably require Koha to use the RabbitMQ REST API (plugin). While it's not necessarily an out-of-the-box solution, I think it is a reasonable one.) > Also, shouldn't we add a rabbitmq status indicator on the about page? +1 I would really like this -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
