https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41506
--- Comment #17 from Victor Grousset/tuxayo <[email protected]> --- (In reply to Oliver Behnke from comment #2) > Yes, please, even if it's only because of this: > > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39314#c10 Yes, the upgrade issue will keep happening. It might be possible to get away with wiping the instance and creating a new DB but that's still additional sysadmin work on an OS upgrade. I wonder how bad that is for small self hosted libraries. Like if until recently it was really possible to upgrade the OS without Koha related stuff ever complaining about anything. And now RabbitMQ will likely almost always cause issues. ----- Does anyone remember feedback from any library noticing more timely background jobs with the switch to RabbitMQ? Or not having FIFO order respected? +1 to remove, having to ask the above question is quite telling ^^" ---- (In reply to David Cook from comment #6) > [...] Basically, I think RabbitMQ > provides us with a lot of power and potential to carry Koha into the future. > However, I also acknowledge that a lot of people don't like it and don't > want it in Koha, and maybe it's overkill for what we need in Koha at > present. Until that future will be more clear, having jumped early into a specific solution might not even help that much. That shot in the dark turned out to be a miss in the present without much hope to hit in the future. -- You are receiving this mail because: You are the assignee for the bug. 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/
