August 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

Add warning in IE that Koha does not support IE
by dcook＠prosentient.com.au 27 Aug '20

27 Aug '20

Hi all, I don't know about you, but I have received a lot of calls about Koha not working in IE 11. Now I think that it is wise that we no longer support IE 11, especially since Microsoft itself is dropping support for it in November 2020, but I think warning people is not a bad idea. I've opened https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26305 to do just that. Keen to get feedback / signoffs. Cheers, David Cook Software Engineer Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

1 0

Self-checkout uses issuing rules rather than renewal rules for renewals
by dcook＠prosentient.com.au 26 Aug '20

26 Aug '20

I had a librarian report that they got stuck in a loop when trying to renew overdue items via the self-checkout. I've written a patch at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26301, and I'm keen to get testers. The self-checkout isn't very straightforward, so I hope others can make sure I didn't miss anything. Doing checkouts and renewals looks good to me so far though. Cheers, David Cook Software Engineer Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

1 0

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

Move .tt files out of "htdocs" and into separate "tt" or "templates" directory
by dcook＠prosentient.com.au 18 Aug '20

18 Aug '20

Hi all, We should move all the .tt files out of the /usr/share/koha/intranet/htdocs and /usr/share/koha/opac/htdocs directories and put them somewhere private like /usr/share/koha/tt or /usr/share/koha/templates. At the moment, Apache is serving these files to anyone who asks for them, and it really shouldn't. Having these files in the "htdocs" directories also makes it harder to manage actual static assets that are served to Koha users. I've opened a Bugzilla report for it: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26140 This early in the release cycle, it could be great to get this done, so that we have a chance to work out any kinks before November. What do people think? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

2 2

Time to translate: string freeze for 19.05.x has begun
by Victor Grousset/tuxayo 17 Aug '20

17 Aug '20

Hi, saluton, hola, bonjour, String freeze will be into effect tomorrow 18 August 2020 for the 19.05.x maintenance branch. (as well as for the other branches) The 19.05.14 release is scheduled for Monday 25 August 2020. Which means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Important reminder: if you add or change a translation in version 19.05, then you must also copy it to 19.11 and 20.05. Otherwise your work will be lost when upgrading to these next versions or the future ones. Happy translating, -- Victor Grousset/tuxayo

1 0

String freeze for 19.11.x
by Aleisha Amohia 17 Aug '20

17 Aug '20

Hi all, String freeze will go into effect end of on Tuesday 18 August 2020 for the 19.11.x maintenance branch. 19.11.09 release scheduled for Tuesday 25 August 2020. Thanks -- Aleisha Amohia (she/her) Koha Developer Catalyst IT - Expert Open Source Solutions

1 0

Call for news: August 2020 Koha Newsletter
by Koha Newsletter 14 Aug '20

14 Aug '20

I'm collecting news for the August newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- ** For events **: - Please include dates for past events. If I can't find dates I may not add it. - Announcements for future events with dates T.B.A. are fine ...Eg., Kohacon - For past events , **** one month back is the cut-off ****. * News items can be of any length. * Images are fine * Anything and everything Koha. * Submit by the 26th of the month. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. Thank you! -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Assigning TCP ports to per-instance Koha services (e.g. koha-sip)
by dcook＠prosentient.com.au 13 Aug '20

13 Aug '20

Hi all, I've noticed that "koha-sip" will copy /etc/koha/SIPconfig.xml into /etc/koha/sites/${name}/SIPconfig.xml, but it retains the default port of 6001. Obviously, only 1 service can bind to port 6001 inside the same network namespace, so that's only going to work once, and any following "koha-sip --enable" will need manual intervention after. Is this a convention that we should expect for all current and future per-instance Koha services using TCP ports? Or should we be thinking about ways of dynamically allocating free ports? I suppose that most multi-Koha installations will have a vendor/service provider who can easily configure backend systems, whereas many organisations without technical expertise are more likely to run only 1 Koha instance (and thus benefit from single hard-coded defaults). So maybe just hard-coding a default into a per-instance Koha service makes sense? Or having an option on CLI scripts like koha-sip to define a port (to ease things for vendors) while leaving the default for users with less complex requirements? Just curious what people think. David Cook Software Engineer Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

3 3