https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39277 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook@prosentient.com.au --- Comment #1 from David Cook <dcook@prosentient.com.au> --- (In reply to Tomás Cohen Arazi (tcohen) from comment #0)
Our current packaging schema is somehow messing with our deployment.
I have run
```shell systemctl stop rabbitmq-server systemctl disable rabbitmq-server ```
but after any routine upgrade it gets enabled again.
I haven't tracked it down but felt it was worth reporting.
When you say "any routine upgrade", do you mean an upgrade of rabbitmq-server, koha-common, or any other package? With Tomcat, I had an issue where I wanted to install the software, but it would automatically start itself up at install time, so I had to create a /usr/sbin/policy-rc.d file to explicitly forbid it from starting up automatically via invoke-rc.d. But that was a different scenario. We do the following: debian/koha-common.postinst:rabbitmq-plugins enable rabbitmq_stomp debian/koha-common.postinst:service rabbitmq-server restart Maybe we should be using "invoke-rc.d rabbitmq-server restart" instead there so it's easier to block where necessary.
There's also the situation you cannot install Koha via packages without requiring rabbitmq, which is also problematic.
Even if you want to use it, we need more fine-grained control. Take Docker as an example, in that context you want to run rabbit on a separate container, or even reuse a single service for many (possibly remote) Koha instances. We shouldn't be requiring it at all on a default setup.
In that case, you can use the "koha-core" package, which just installs the Koha app and its system utilities and client libraries. Docker was one of the things I was thinking of when I first proposed the "koha-core" package. We probably haven't updated koha-common to depend on koha-core because it would cause issues when using "apt-get install koha-common"... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.