<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>A new request with request id 8868 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 199, Issue 17<br>Category : <br>Description : <div>Send Koha-devel mailing list submissions to<br> koha-devel@lists.koha-community.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>or, via email, send a message with subject or body 'help' to<br> koha-devel-request@lists.koha-community.org<br><br>You can reach the person managing the list at<br> koha-devel-owner@lists.koha-community.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Koha-devel digest..."<br><br><br>Today's Topics:<br><br> 1. Re: Distributing Koha Plugins efficiently (Michael Hafen)<br> 2. SIP server only supporting 1 simultaneous connection (Bug<br> 31033) (dcook@prosentient.com.au)<br> 3. Re: Distributing Koha Plugins efficiently<br> (dcook@prosentient.com.au)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Thu, 23 Jun 2022 10:16:19 -0600<br>From: Michael Hafen <michael.hafen@washk12.org><br>To: dcook@prosentient.com.au<br>Cc: koha-devel <koha-devel@lists.koha-community.org>, Tomas Cohen<br> Arazi <tomascohen@theke.io>, Kyle Hall <kyle@bywatersolutions.com><br>Subject: Re: [Koha-devel] Distributing Koha Plugins efficiently<br>Message-ID:<br> <CAAh7Udmn=-ZnD8vwnQZPexdTsrOJdbtdOV9FPjTbRdPnJzJGBw@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>That's basically what I have done, except that I distribute my plugins to<br>my servers from my git repo.<br><br>On Wed, Jun 22, 2022 at 9:52 PM <dcook@prosentient.com.au> wrote:<br><br>> Hi all,<br>><br>><br>><br>> If I were to unpack 5 different Koha plugins to /opt/koha-plugins and then<br>> added "<pluginsdir>/opt/koha-plugins</pluginsdir>" to the koha-conf.xml for<br>> all my Koha instances, I should be able to just run “koha-foreach perl<br>> /usr/share/koha/bin/devel/install_plugins.pl” to install/upgrade all<br>> those plugins within Koha, right?<br>><br>><br>><br>> Once “bug 21366 – add plack reload” is done, we could then do “koha-plack<br>> --reload $(koha-list --enabled --plack)” to gracefully reload all those<br>> Koha instances to have the freshest version of the plugin.<br>><br>><br>><br>> --<br>><br>><br>><br>> If that’s true, a person could bundle Koha plugins however they like,<br>> right? They could put them into koha-common, they could do their own<br>> koha-plugins package (included or separate to their Koha codebase), they<br>> could just use a Git repo, or whatever makes sense for distributing. The<br>> advantage of Debian packages would be adding that “koha-foreach” and<br>> “koha-plack” into package install hooks.<br>><br>><br>><br>> I suppose a “install plugins” hook in “koha-create” would be wise too so<br>> that a new instance could auto install any centralized plugins…<br>><br>><br>><br>> Does that all make sense? Am I missing anything?<br>><br>><br>><br>> I’d really like to use plugins in lieu of Koha customizations but I find<br>> distributing the code across a large number of Koha instances to be<br>> prohibitive.<br>><br>><br>><br>> David Cook<br>><br>> Senior Software Engineer<br>><br>> Prosentient Systems<br>><br>> Suite 7.03<br>><br>> 6a Glen St<br>><br>> Milsons Point NSW 2061<br>><br>> Australia<br>><br>><br>><br>> Office: 02 9212 0899<br>><br>> Online: 02 8005 0595<br>><br>><br>> _______________________________________________<br>> Koha-devel mailing list<br>> Koha-devel@lists.koha-community.org<br>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>> website : https://www.koha-community.org/<br>> git : https://git.koha-community.org/<br>> bugs : https://bugs.koha-community.org/<br>><br><br><br>-- <br>Michael Hafen<br>Washington County School District Technology Department<br>Systems Analyst<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220623/58522856/attachment-0001.htm><br><br>------------------------------<br><br>Message: 2<br>Date: Fri, 24 Jun 2022 11:50:38 +1000<br>From: <dcook@prosentient.com.au><br>To: "'koha-devel'" <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] SIP server only supporting 1 simultaneous<br> connection (Bug 31033)<br>Message-ID: <03b801d8876c$d04b6790$70e236b0$@prosentient.com.au><br>Content-Type: text/plain; charset="utf-8"<br><br>Hi all,<br><br> <br><br>I was going through my emails when I noticed Bug 31033, which indicates that<br>Koha's SIP server only supports 1 simultaneous connection of the box.<br><br> <br><br>I did some testing and confirmed Mark's findings. Honestly, I'd never<br>thought about it. While we do run some SIP servers, it's never come up as an<br>issue.<br><br> <br><br>Have folk noticed the same thing and do they just resolve the problem by<br>updating their SIPconfig.xml files? <br><br> <br><br>I've added a patch to Bug 31033 to make Koha's default configuration more<br>explicit, but curious what people's thoughts are.<br><br> <br><br>David Cook<br><br>Senior Software Engineer<br><br>Prosentient Systems<br><br>Suite 7.03<br><br>6a Glen St<br><br>Milsons Point NSW 2061<br><br>Australia<br><br> <br><br>Office: 02 9212 0899<br><br>Online: 02 8005 0595<br><br> <br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220624/613c2ae4/attachment-0001.htm><br><br>------------------------------<br><br>Message: 3<br>Date: Fri, 24 Jun 2022 12:01:57 +1000<br>From: <dcook@prosentient.com.au><br>To: "'Michael Hafen'" <michael.hafen@washk12.org><br>Cc: "'koha-devel'" <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Distributing Koha Plugins efficiently<br>Message-ID: <03bf01d8876e$66758600$33609200$@prosentient.com.au><br>Content-Type: text/plain; charset="utf-8"<br><br>Thanks for replying, Michael. I am leaning towards a Git repo as well for the sake of simplicity. I imagine you have a script in that repo for running “koha-foreach perl /usr/share/koha/bin/devel/install_plugins.pl”, restarts, etc?<br><br> <br><br>David Cook<br><br>Senior Software Engineer<br><br>Prosentient Systems<br><br>Suite 7.03<br><br>6a Glen St<br><br>Milsons Point NSW 2061<br><br>Australia<br><br> <br><br>Office: 02 9212 0899<br><br>Online: 02 8005 0595<br><br> <br><br>From: Michael Hafen <michael.hafen@washk12.org> <br>Sent: Friday, 24 June 2022 2:16 AM<br>To: dcook@prosentient.com.au<br>Cc: koha-devel <koha-devel@lists.koha-community.org>; Tomas Cohen Arazi <tomascohen@theke.io>; Kyle Hall <kyle@bywatersolutions.com><br>Subject: Re: [Koha-devel] Distributing Koha Plugins efficiently<br><br> <br><br>That's basically what I have done, except that I distribute my plugins to my servers from my git repo.<br><br> <br><br>On Wed, Jun 22, 2022 at 9:52 PM <dcook@prosentient.com.au <mailto:dcook@prosentient.com.au> > wrote:<br><br>Hi all,<br><br> <br><br>If I were to unpack 5 different Koha plugins to /opt/koha-plugins and then added "<pluginsdir>/opt/koha-plugins</pluginsdir>" to the koha-conf.xml for all my Koha instances, I should be able to just run “koha-foreach perl /usr/share/koha/bin/devel/install_plugins.pl <http://install_plugins.pl> ” to install/upgrade all those plugins within Koha, right?<br><br> <br><br>Once “bug 21366 – add plack reload” is done, we could then do “koha-plack --reload $(koha-list --enabled --plack)” to gracefully reload all those Koha instances to have the freshest version of the plugin. <br><br> <br><br>--<br><br> <br><br>If that’s true, a person could bundle Koha plugins however they like, right? They could put them into koha-common, they could do their own koha-plugins package (included or separate to their Koha codebase), they could just use a Git repo, or whatever makes sense for distributing. The advantage of Debian packages would be adding that “koha-foreach” and “koha-plack” into package install hooks. <br><br> <br><br>I suppose a “install plugins” hook in “koha-create” would be wise too so that a new instance could auto install any centralized plugins…<br><br> <br><br>Does that all make sense? Am I missing anything?<br><br> <br><br>I’d really like to use plugins in lieu of Koha customizations but I find distributing the code across a large number of Koha instances to be prohibitive. <br><br> <br><br>David Cook<br><br>Senior Software Engineer<br><br>Prosentient Systems<br><br>Suite 7.03<br><br>6a Glen St<br><br>Milsons Point NSW 2061<br><br>Australia<br><br> <br><br>Office: 02 9212 0899<br><br>Online: 02 8005 0595<br><br> <br><br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> <br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br><br><br>-- <br><br>Michael Hafen<br><br>Washington County School District Technology Department<br><br>Systems Analyst<br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220624/2ee1e806/attachment.htm><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>End of Koha-devel Digest, Vol 199, Issue 17<br>*******************************************<br></div><br><br>NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.<br></body></html>