https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417
--- Comment #254 from Jonathan Druart <[email protected]> --- (In reply to Julian Maurice from comment #252) > (In reply to Marcel de Rooy from comment #250) > > If we feel that RabbitMQ is not ready for primary processes like the batch > > record modify in this patch set, we should remove that part. I would not > > promote a hybrid solution that falls back to code without MQ. It should just > > be stable enough to operate on and seen as an essential component. > > It's not about stability. I'm sure RabbitMQ is stable enough for this. > It's about not adding another mandatory dependency when we don't need it. Do > I really need a message queue if I run 1 background job per day ? > Of course a MQ will be useful to some. I'm not advocating against it. I'm > only saying a fallback would be nice for those who only run jobs > occasionally. > Also the upgrade path would be simpler ("just make sure the script worker.pl > is always running and you're good") So you think the last patch is the (kind of) way to go? (In reply to Julian Maurice from comment #253) > (In reply to Jonathan Druart from comment #251) > > So far there is no configuration, the default parameters are used and > > hardcoded in the connection method. > > That should probably be changed if, as someone already mentioned, one want > to install rabbitmq on another server, or in a different docker container, > ... Yes, see bug 25674 ;) -- 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/
