June 2020 - Koha-devel - lists.koha-community.org

How to make self-referential URLs in Koha
by dcook＠prosentient.com.au 30 Jan '23

30 Jan '23

Hi all, With some recent code, I've been using creating self-referential URL in Koha using CGI->url(), and passing it as a value. With CGI, the URL is correct (ie starting with /cgi-bin/koha). With Plack, it's not, because the OPAC is mounted as "/opac". I worked around this by rewriting the self-referential URL in my code, but I was wondering if anyone else had any thoughts on this. I've noticed there are a few places in Koha where we use CGI->url() and I'm guessing we may have unexpected bugs in Plack-enabled Koha as a result. Of course, one workaround would be to have /opac and /intranet aliases or URL rewriting in Apache, so that the self-referential URLs created by Plack still end up resolving. I wonder if that's the easiest path forward. In the past, I have wondered if we could get rid of "/cgi-bin/koha" as a path prefix all together (especially as cgi-bin scares security tools), but it's so deeply embedded in Koha at this point that it seems a huge task to replace it. Anyway, just throwing that out there. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

6 8

String Freeze Notice
by Joy Nelson 12 Aug '22

12 Aug '22

Greetings! Just a quick note that string freeze will go into effect at the end of day 12/16/2019 for the maintenance branches. Maintenance releases scheduled for the 23rd. Translations can begin on the 17th. Thanks! -- Joy Nelson President, Koha Division ByWater Solutions <http://bywatersolutions.com> Support and Consulting for Open Source Software Phone/Fax (888)900-8944 What is Koha? <http://bywatersolutions.com/what-is-koha/>

3 3

Deploying Koha at scale
by Tomás 19 Aug '20

19 Aug '20

Hi folks. Theke Solutions has started a project some time ago, sponsored by ByWater Solutions to generate the tools and pipelines to provide a reliable Docker implementation for deploying Koha in production environments. We have just finished the housekeeping a few days ago so we are not embarrassed by our commit messages and leftovers :-D and want to propose it for community adoption anytime soon. The project lives here for now: https://gitlab.com/thekesolutions/koha-docker What you will find there is a Docker image that can be used to run any of the different Koha services/pieces on separate containers, or all inside a single one. We aimed to target different deployment scenarios, from a small library running it on a desktop computer to a multi-cluster K8s setup. A helm chart is part of the roadmap. You will notice there are a couple issues to be addressed [1]. For instance, the shipped docker-compose.yml is outdated regarding the MySQL/MariaDB server and we definitely need more on the README. Thanks to ByWater for supporting this effort, and now that people are talking about this, let's start the conversation \o/ [1] https://gitlab.com/thekesolutions/koha-docker/-/issues El jue., 11 jun. 2020 a las 4:52, <dcook(a)prosentient.com.au> escribió: > Hi all, > > For a long time, I've been thinking about how Koha could scale better, and > I'm wondering what other people are thinking about this topic. I think > Mengu > is probably the best expert on this topic that we have on Earth, so > especially curious about his input. > > It's relatively easy to add more Apache web servers, more MySQL nodes, and > more Elasticsearch nodes. but the same might not be said for other parts of > Koha like the following: > > 1. Zebra > a. In theory, you could load balance queries to a cluster of Zebra > listeners > b. But indexing updates to many Zebra databases could be tricky (I > don't know if Zebra's database can support many readers). I suppose you > could alter rebuild_zebra.pl to update multiple databases in a variety of > different ways. I imagine Mengu could speak to this, as I recall him > talking > once about needing to do work to make Zebra scale? > > 2. I'm not familiar enough with the SIP server to say > a. Off the top of my head, I think a TCP load balancer would be > good > enough here > > 3. Z3950 Responder? > a. I'm not familiar with this daemon > > 4. What about cronjobs? Only 1 instance should execute the cronjobs. > a. I suppose a person could disable cronjobs on all Koha nodes > except for 1? It wouldn't be very robust in terms of availability but it > would technically work most of the time. > > Any other thoughts? > > David Cook > Systems Librarian > Prosentient Systems > 72/330 Wattle St > Ultimo, NSW 2007 > Australia > > Office: 02 9212 0899 > Online: 02 8005 0595 > > > -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

4 4

Re: [Koha-devel] [Koha] Koha 19.11.07 released
by Aleisha Amohia 30 Jun '20

30 Jun '20

Hi Alvaro Looks like the packaging manager hasn't built the new packages yet. I am sure they will email the list when those are ready! Thanks for bringing it to our attention, and apologies for the delay. Aleisha On 30/06/20 4:46 pm, Alvaro Cornejo wrote: > Hi > > Does debian packages have been released? > > I was getting this message on apt-get update > > E: Repository 'http://debian.koha-community.org/koha stable InRelease' > changed its 'Codename' value from '19.11' to '20.05' > > So I changed: > > koha.list to > deb http://debian.koha-community.org/koha 19.11 main > > From > deb http://debian.koha-community.org/koha stable main > > Now I get this on apt-get update > > Get:8 http://debian.koha-community.org/koha 19.11/main amd64 Packages > [20.4 kB] > Get:9 http://debian.koha-community.org/koha 19.11/main i386 Packages > [18.5 kB] > Fetched 88.3 kB in 1s (119 kB/s) > > But apt-get upgrade gives me nothing to update. > > Regards, > > Alvaro > > > > |----------------------------------------------------------------------------------------| > Stay safe / Cuídate/ Reste sécurisé > */7/* Switch off as you go / Apaga lo que no usas / Débranchez au fur > et à mesure. > *q *Recycle always / Recicla siempre / Recyclez toujours > P Print only if absolutely necessary / Imprime solo si es necesario / > Imprimez seulement si nécessaire > > > Le lun. 22 juin 2020 à 23:01, Aleisha Amohia <aleisha(a)catalyst.net.nz > <mailto:aleisha@catalyst.net.nz>> a écrit : > > Hello! > > The Koha community is proud to announce the release of Koha 19.11.07. > > Koha 19.11.07 is a bugfix/maintenance release that includes 2 > enhancements and 48 bugfixes. > > Full release notes can be found here: > https://koha-community.org/koha-19-11-07-released/ > > This is my first release! :D > > -- > *Aleisha Amohia* > Koha Developer > > Catalyst IT - Expert Open Source Solutions > She/her | Mob: +64 21 024 04004 | Tel: +64 4 499 2267 | > www.catalyst.net.nz <http://www.catalyst.net.nz> > <http://www.catalyst.net.nz> > > Catalyst Logo > > CONFIDENTIALITY NOTICE: This email is intended for the named > recipients > only. It may contain privileged, confidential or copyright > information. > If you are not the named recipient, any use, reliance upon, disclosure > or copying of this email or its attachments is unauthorised. If > you have > received this email in error, please reply via email or call +64 4 > 499 2267. > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > --

2 1

Koha Community Newsletter: June 2020
by Koha Newsletter 30 Jun '20

30 Jun '20

The Koha Community Newsletter for June 2020 is here: https://koha-community.org/koha-community-newsletter-june-2020/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Recalls for Koha, Bug 19532
by Aleisha Amohia 29 Jun '20

29 Jun '20

Hi everyone, I would love to get recalls through in the 20.11 cycle. The feature on Bug 19532 is currently in production for a few tertiary libraries, one of which has been using it for about 2 years now! Definitely time to get it into master. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19532 It is a fully functioning feature now (as we've been developing and building on it for years) so the test plan is quite long, but I'd really appreciate someone taking the time to test it and let me know what needs to be done to get it through. The test plan is on Comment 482 (yes, 482!). It is also fully documented at https://wiki.koha-community.org/wiki/Catalyst_IT_Recalls I've rebased the patches again to apply on master. Looking forward to getting some movement on this! -- *Aleisha Amohia* Koha Developer Catalyst IT - Expert Open Source Solutions She/her | Mob: +64 21 024 04004 | Tel: +64 4 499 2267 | www.catalyst.net.nz <http://www.catalyst.net.nz> Catalyst Logo CONFIDENTIALITY NOTICE: This email is intended for the named recipients only. It may contain privileged, confidential or copyright information. If you are not the named recipient, any use, reliance upon, disclosure or copying of this email or its attachments is unauthorised. If you have received this email in error, please reply via email or call +64 4 499 2267.

1 0

Perl version requirement
by Julian Maurice 27 Jun '20

27 Jun '20

Hi, While reading the release notes for 20.05.01 I noticed that the minimum Perl version required is still 5.10. However, we use the '/r' regex modifier which was introduced in 5.14. There may be other features that we use that are not in Perl 5.10. Considering that even debian oldstable has Perl 5.24, it should be safe to raise the minimum required version to 5.24. What do you think ? -- Julian Maurice BibLibre

10 16

Facets sorting
by Fridolin SOMERS 26 Jun '20

26 Jun '20

Hi, I'm working on the behavior of facets. Actually values are sorted alphabeticaly in Zebra and by nb of occurences in Elasticsearch. Looking for opinions on : https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25838 Best regards, -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> Software and system maintainer 🦄 BibLibre, France

2 1

Want separate timestamped error log files for Plack? You got it.
by dcook＠prosentient.com.au 26 Jun '20

26 Jun '20

Hi all, Tired of going to plack-error.log and getting output for every Plack app without any timestamps? Not sure if the output is from the Intranet or the OPAC? Not sure what time it happened? Well suffer no more! Go to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16357 and check out the two "[Alternative]" patches that I've posted there. Rejoice in having separate log files for the Intranet, OPAC, and API including timestamps. All this and more for the low low cost of following the test plan I've provided on Bugzilla and signing off those 2 patches. Cheers! David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

1 0

Perl 7
by dcook＠prosentient.com.au 26 Jun '20

26 Jun '20

For those who don't know, Perl 7 was just announced yesterday: https://www.perl.com/article/announcing-perl-7/ I've talked about this in the "Perl version requirement" thread but basically it boils down to "Perl 7 is v5.32 with different settings. Your code should work if it's not a mess. Expect a user release within a year." The article is worth a read though. It points out a number of language aspects that have changed (e.g. bareword file handles, indirect object notation, etc), and we could actually work on eliminating those in our current code to bring Koha more in line with modern Perl. While we're still years away from moving Koha over to this hypothetical Perl 7, it's something to look forward to. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

4 5