<!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 18939 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 185, Issue 13<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. Elasticsearch vs OpenSearch (dcook@prosentient.com.au)<br> 2. Re: Packaging idea (for decoupling systems, Docker, etc)<br> (Mason James)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Fri, 16 Apr 2021 10:23:17 +1000<br>From: <dcook@prosentient.com.au><br>To: <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] Elasticsearch vs OpenSearch<br>Message-ID: <049201d73256$b25a7d50$170f77f0$@prosentient.com.au><br>Content-Type: text/plain; charset="utf-8"<br><br>Because I'm good at stirring up trouble.<br>https://www.techrepublic.com/google-amp/article/opensearch-aws-rolls-out-its<br>-open-source-elasticsearch-fork/ <br><br> <br><br>As you may know, AWS have forked the last FOSS Elasticsearch (7.10 I think).<br>They've announced that they're calling it OpenSearch. It's still only in<br>alpha stage and they won't have a production-ready release for months yet,<br>but it is interesting to keep notes on.<br><br> <br><br>Elastic are responsible for the vast majority of commits in Elasticsearch,<br>so I'm somewhat skeptical about a fork, but I think there is a lot of anger<br>at Elastic and a lot of support for OpenSearch, so who knows. <br><br> <br><br>I don't think there's anything to do at this stage, but just wanted to share<br>the information for people <br><br> <br><br>David Cook<br><br>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/20210416/25b76505/attachment-0001.htm><br><br>------------------------------<br><br>Message: 2<br>Date: Fri, 16 Apr 2021 17:50:08 +1200<br>From: Mason James <mtj@kohaaloha.com><br>To: koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] Packaging idea (for decoupling systems,<br> Docker, etc)<br>Message-ID: <97cef079-20b5-30c0-0bdc-3b96382a2cef@kohaaloha.com><br>Content-Type: text/plain; charset=windows-1252; format=flowed<br><br>hi David<br><br>i think we may already have this functionality with the 'koha-core' package?<br><br><br>On 15/04/21 3:32 pm, dcook@prosentient.com.au wrote:<br>><br>> Hey all,<br>><br>> What do people think about creating a “koha-libs” package which just contains Koha’s libraries (ie C4/, Koha/, etc)?<br>><br>> I’m not as familiar with DEB packaging as I am with RPM packaging, but I recently did it with a RPM-based project I manage. It allowed me to easily create other services with the same dependencies. I created these other services in other Docker containers, and I was able to use my core application libraries without having to install the entire application in every container. I share the application configuration file between them and that’s it.<br>><br>> It’s not a perfect solution. Really what I want is app-service1, app-service2, app-service3, and app-common with app-common containing the shared libraries. But I like it as an intermediate step.<br>><br>> And I would be lying if it didn’t have pros and cons. One con is updating a library in app-libs, when I need a change in app-service1, and then making sure that all my deployments have the right updated library. More overhead than just having a monolithic application. On the other hand, if I want to make a change just to app-service1, I can just update it without having to affect any other parts of the application. That added overhead also gives incentive for writing cleaner testable code which does the right thing in the first place.<br>><br>> Anyway, just food for thought.<br>><br>> David Cook<br>><br>> 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>> 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><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 185, Issue 13<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>