From kohanews at gmail.com Sat Feb 1 04:08:50 2020 From: kohanews at gmail.com (kohanews) Date: Fri, 31 Jan 2020 19:08:50 -0800 Subject: [Koha-devel] Koha Community Newsletter: January 2020 Message-ID: <884cef58-ebbf-7614-f483-c8a17a0bdc7e@gmail.com> The Koha Community Newsletter for January 2020 is here: https://koha-community.org/koha-community-newsletter-january-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 From indradg at l2c2.co.in Sun Feb 2 09:06:36 2020 From: indradg at l2c2.co.in (Indranil Das Gupta) Date: Sun, 2 Feb 2020 13:36:36 +0530 Subject: [Koha-devel] Trouble in setting up kohadevbox on Win10 prof Message-ID: Hi all, I'm trying to setup kohadevbox on a Windows 10 prof laptop. I'm going after stretch64 Things I've done so far: 1. I had to switch the distribution to https://app.vagrantup.com/digital-port/boxes/debian-stretch64 because otherwise I was hitting the missing linux-headers for vbox guest additions. 2. Ran SMB=1 SKIP_WEBINSTALLER=1 CREATE_ADMIN_USER=1 LOCAL_ANSIBLE=1 SYNC_REPO="/home/vagrant/kohaclone" vagrant up 3. I've the VM created, can ssh into it both as `vagrant ssh` as well as via putty 4. But no cheese when i try to access http://localhost:8081 either inside the VM or from my host box 5. the .deb installation did go through, because there is /usr/share/koha and the koha-* commands are accessible e.g. koha-list. koha-passwd so package got installed. 6. /home/vagrant/kohaclone is empty and that I guess is the root of my problems because the installation has gotten gitified and there is nothing there at the moment. 7. I'm now manually doing a `git clone http://git.koha-community.org/koha.git kohaclone` in /home/vagrant to see if that makes a difference. My question: kohadevbox README.md says - "A clone of the official Koha Git repo, or a NFS-mounted git repository from your host machine." So what am I missing here? Cluesticks / brickbats welcome... and expected :-) thanks -- Indranil Das Gupta L2C2 Technologies Phone : +91-98300-20971 WWW : http://www.l2c2.co.in Blog : http://blog.l2c2.co.in IRC : indradg on irc://irc.freenode.net Twitter : indradg -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Mon Feb 3 00:31:03 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Mon, 3 Feb 2020 10:31:03 +1100 Subject: [Koha-devel] Trouble in setting up kohadevbox on Win10 prof In-Reply-To: References: Message-ID: <0ab001d5da20$d592e440$80b8acc0$@prosentient.com.au> Hey Indranil, I’m not sure if kohadevbox is getting much love and attention, especially on Windows, anymore. Happy to be corrected if I’m wrong but I think many people are moving / have moved to koha-testing-docker: https://gitlab.com/koha-community/koha-testing-docker. The documentation could use a bit of work but you can update the KOHA_IMAGE variable to pick different images available from https://hub.docker.com/r/koha/koha-testing/tags (I actually just noticed that this moment). My guess is “master” is for stretch since there are master-jessie and master-buster available as well. Personally, I use Docker Desktop on Windows, and I find mounting a volume with my Git can be painful, so I actually just created a named volume (within the Docker Desktop VM) and keep my Git clone there. That way it’s just all Linux all the time. Alas, I deleted my last kohadevbox recently, so can’t help you on that one, I’m afraid. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Koha-devel On Behalf Of Indranil Das Gupta Sent: Sunday, 2 February 2020 7:07 PM To: Koha-devel Subject: [Koha-devel] Trouble in setting up kohadevbox on Win10 prof Hi all, I'm trying to setup kohadevbox on a Windows 10 prof laptop. I'm going after stretch64 Things I've done so far: 1. I had to switch the distribution to https://app.vagrantup.com/digital-port/boxes/debian-stretch64 because otherwise I was hitting the missing linux-headers for vbox guest additions. 2. Ran SMB=1 SKIP_WEBINSTALLER=1 CREATE_ADMIN_USER=1 LOCAL_ANSIBLE=1 SYNC_REPO="/home/vagrant/kohaclone" vagrant up 3. I've the VM created, can ssh into it both as `vagrant ssh` as well as via putty 4. But no cheese when i try to access http://localhost:8081 either inside the VM or from my host box 5. the .deb installation did go through, because there is /usr/share/koha and the koha-* commands are accessible e.g. koha-list. koha-passwd so package got installed. 6. /home/vagrant/kohaclone is empty and that I guess is the root of my problems because the installation has gotten gitified and there is nothing there at the moment. 7. I'm now manually doing a `git clone http://git.koha-community.org/koha.git kohaclone` in /home/vagrant to see if that makes a difference. My question: kohadevbox README.md says - "A clone of the official Koha Git repo, or a NFS-mounted git repository from your host machine." So what am I missing here? Cluesticks / brickbats welcome... and expected :-) thanks -- Indranil Das Gupta L2C2 Technologies Phone : +91-98300-20971 WWW : http://www.l2c2.co.in Blog : http://blog.l2c2.co.in IRC : indradg on irc://irc.freenode.net Twitter : indradg -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From clopez at dml.vic.edu.au Mon Feb 3 01:43:58 2020 From: clopez at dml.vic.edu.au (Carlos Lopez) Date: Mon, 3 Feb 2020 00:43:58 +0000 Subject: [Koha-devel] Trouble in setting up kohadevbox on Win10 prof In-Reply-To: References: Message-ID: Hi Indranil I’ve never tried to do this so please don’t take it as expert advice. What I would do would be (from the VM) to check whether you have a firewalld rule to allow access to port 8081, and if you’re already allowing access to that port to see whether Apache is installed and working properly (and while you’re at it you might see whether MySQL/MariaDB is installed and working properly as well). With kind regards from the Dalton McCaughey Library Team Carlos Lopez Dalton McCaughey Library | 29 College Crescent, Parkville, VICTORIA 3052 Ph: 03 9340 8888 ext.1 | library at dml.vic.edu.au | library.dmlibrary.org.au From: Koha-devel On Behalf Of Indranil Das Gupta Sent: Sunday, 2 February 2020 7:07 PM To: Koha-devel Subject: [Koha-devel] Trouble in setting up kohadevbox on Win10 prof Hi all, I'm trying to setup kohadevbox on a Windows 10 prof laptop. I'm going after stretch64 Things I've done so far: 1. I had to switch the distribution to https://app.vagrantup.com/digital-port/boxes/debian-stretch64 because otherwise I was hitting the missing linux-headers for vbox guest additions. 2. Ran SMB=1 SKIP_WEBINSTALLER=1 CREATE_ADMIN_USER=1 LOCAL_ANSIBLE=1 SYNC_REPO="/home/vagrant/kohaclone" vagrant up 3. I've the VM created, can ssh into it both as `vagrant ssh` as well as via putty 4. But no cheese when i try to access http://localhost:8081 either inside the VM or from my host box 5. the .deb installation did go through, because there is /usr/share/koha and the koha-* commands are accessible e.g. koha-list. koha-passwd so package got installed. 6. /home/vagrant/kohaclone is empty and that I guess is the root of my problems because the installation has gotten gitified and there is nothing there at the moment. 7. I'm now manually doing a `git clone http://git.koha-community.org/koha.git kohaclone` in /home/vagrant to see if that makes a difference. My question: kohadevbox README.md says - "A clone of the official Koha Git repo, or a NFS-mounted git repository from your host machine." So what am I missing here? Cluesticks / brickbats welcome... and expected :-) thanks -- Indranil Das Gupta L2C2 Technologies Phone : +91-98300-20971 WWW : http://www.l2c2.co.in Blog : http://blog.l2c2.co.in IRC : indradg on irc://irc.freenode.net Twitter : indradg Report this message as spam -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Mon Feb 3 10:37:28 2020 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Mon, 3 Feb 2020 10:37:28 +0100 Subject: [Koha-devel] Trouble in setting up kohadevbox on Win10 prof In-Reply-To: References: Message-ID: Hi Indranil, On `vagrant up` you need to set SYNC_REPO to a path pointing to the Koha src. You set "/home/vagrant/kohaclone", which does not seem correct. That must be something like /home/$USER/kohaclone (replace that with a windows path) Cheers, Jonathan Le dim. 2 févr. 2020 à 09:06, Indranil Das Gupta a écrit : > > Hi all, > > I'm trying to setup kohadevbox on a Windows 10 prof laptop. I'm going after stretch64 > > Things I've done so far: > > 1. I had to switch the distribution to https://app.vagrantup.com/digital-port/boxes/debian-stretch64 because otherwise I was hitting the missing linux-headers for vbox guest additions. > > 2. Ran SMB=1 SKIP_WEBINSTALLER=1 CREATE_ADMIN_USER=1 LOCAL_ANSIBLE=1 SYNC_REPO="/home/vagrant/kohaclone" vagrant up > > 3. I've the VM created, can ssh into it both as `vagrant ssh` as well as via putty > > 4. But no cheese when i try to access http://localhost:8081 either inside the VM or from my host box > > 5. the .deb installation did go through, because there is /usr/share/koha and the koha-* commands are accessible e.g. koha-list. koha-passwd so package got installed. > > 6. /home/vagrant/kohaclone is empty and that I guess is the root of my problems because the installation has gotten gitified and there is nothing there at the moment. > > 7. I'm now manually doing a `git clone http://git.koha-community.org/koha.git kohaclone` in /home/vagrant to see if that makes a difference. > > My question: kohadevbox README.md says - "A clone of the official Koha Git repo, or a NFS-mounted git repository from your host machine." > > So what am I missing here? Cluesticks / brickbats welcome... and expected :-) > > thanks > > -- > Indranil Das Gupta > L2C2 Technologies > > Phone : +91-98300-20971 > WWW : http://www.l2c2.co.in > Blog : http://blog.l2c2.co.in > IRC : indradg on irc://irc.freenode.net > Twitter : indradg > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ From oleonard at myacpl.org Mon Feb 3 14:42:25 2020 From: oleonard at myacpl.org (Owen Leonard) Date: Mon, 3 Feb 2020 08:42:25 -0500 Subject: [Koha-devel] Trouble in setting up kohadevbox on Win10 prof In-Reply-To: References: Message-ID: I used koha-testing-docker on Windows 10 for a while and then it stopped working for me altogether: https://gitlab.com/koha-community/koha-testing-docker/issues/140 > 1. I had to switch the distribution to https://app.vagrantup.com/digital-port/boxes/debian-stretch64 > because otherwise I was hitting the missing linux-headers for vbox guest additions. I switched back to kohadevbox and got it working after some wrangling, but a few days ago it stopped working too. Now I'm seeing what I think you're seeing too: E: Unable to locate package linux-headers-4.9.0-9-amd64 E: Couldn't find any package by glob 'linux-headers-4.9.0-9-amd64' E: Couldn't find any package by regex 'linux-headers-4.9.0-9-amd64' I should have kept better notes about how I got my devbox working before, but it's confusing that it would simply stop working. -- Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org From oleonard at myacpl.org Mon Feb 3 15:59:04 2020 From: oleonard at myacpl.org (Owen Leonard) Date: Mon, 3 Feb 2020 09:59:04 -0500 Subject: [Koha-devel] Trouble in setting up kohadevbox on Win10 prof In-Reply-To: References: Message-ID: Looks like this was the solution I used before. Thanks to whichever person or search engine helped me with it. Sorry I don't remember. I know I didn't come up with it myself. Running this shell script worked for me today: #! /bin/sh export FIRST_RUN='true' vagrant up --no-provision vagrant ssh -c 'sudo apt-get update' vagrant ssh -c 'sudo apt-get upgrade' vagrant ssh -c 'sudo apt-get install -y build-essential linux-headers-amd64 linux-image-amd64 python-apt python-pip' vagrant halt export FIRST_RUN='false' vagrant up I hope that help, -- Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org From mtompset at hotmail.com Mon Feb 3 17:03:08 2020 From: mtompset at hotmail.com (Mark Tompsett) Date: Mon, 3 Feb 2020 11:03:08 -0500 Subject: [Koha-devel] Trouble in setting up kohadevbox on Win10 prof In-Reply-To: References: Message-ID: Greetings, My virtualbox didn’t play nice with Hyper-V. And various windows features keep turning it back on, GRRRR! Hit the Windows Key and type “windows features” Hit the Windows Key + W combo to bring up the Windows Settings panel of the Start Screen. Click on Turn Windows features on or off. When the Turn Windows features on or off dialog appears, look for Hyper-V and deselect it. Click OK. Restart your computer when prompted. dism.exe /Online /Disable-Feature:Microsoft-Hyper-V dism.exe /Online /Disable-Feature:Microsoft-Hyper-V /all Restart your computer. bcdedit /set hypervisorlaunchtype off Restart your computer After that, had some issues as my virtualbox, git bash, and vagrant were out of date. So updated those. Then I was lazy: vagrant up It bombed, because of linux-headers something. vagrant ssh sudo apt install linux-headers exit vagrant halt vagrant up It then correctly provisioned. So, while Owen's shared script may be valid, I'm not sure it is necessary to get too detailed. Also, Jonathan Druart made a good point about the SYNC_REPO path being your local windows path, not the one on the VM. GPML, Mark Tompsett From kohanews at gmail.com Mon Feb 3 19:56:04 2020 From: kohanews at gmail.com (kohanews) Date: Mon, 3 Feb 2020 10:56:04 -0800 Subject: [Koha-devel] Koha Newsletter January 2020: addendum Message-ID: <66e54f3b-34d7-4b8e-4f7b-8deeb544e3d6@gmail.com> I overlooked a really great submission to the Jan. 2020 newsletter. Must be the lack of caffeine. ( Sorry about that, Marcel! ) Please take a look at the newly added entry in the community announcements section of the newsletter: https://koha-community.org/koha-community-newsletter-january-2020/#announce *Marcel de Rooy* blogs about the history and use of Koha at the Rijksmuseum over the last 10 years. Though rare, this isn't the first time I've overlooked tidbits and article submissions over the past few years and I've decided to start announcing my blunders while calling attention to the articles in an email addendum so they get the attention they deserve. Thank you! Chad -- Chad Roseburg Editor, Koha Community Newsletter -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Tue Feb 4 01:10:19 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Tue, 4 Feb 2020 11:10:19 +1100 Subject: [Koha-devel] Trouble in setting up kohadevbox on Win10 prof In-Reply-To: References: Message-ID: <0b4401d5daef$7c342a10$749c7e30$@prosentient.com.au> Damn, sorry to hear that. I have some things to say on that topic, but I'll add them to the Gitlab issue. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -----Original Message----- From: Koha-devel On Behalf Of Owen Leonard Sent: Tuesday, 4 February 2020 12:42 AM To: Koha-devel Subject: Re: [Koha-devel] Trouble in setting up kohadevbox on Win10 prof I used koha-testing-docker on Windows 10 for a while and then it stopped working for me altogether: https://gitlab.com/koha-community/koha-testing-docker/issues/140 > 1. I had to switch the distribution to > https://app.vagrantup.com/digital-port/boxes/debian-stretch64 > because otherwise I was hitting the missing linux-headers for vbox guest additions. I switched back to kohadevbox and got it working after some wrangling, but a few days ago it stopped working too. Now I'm seeing what I think you're seeing too: E: Unable to locate package linux-headers-4.9.0-9-amd64 E: Couldn't find any package by glob 'linux-headers-4.9.0-9-amd64' E: Couldn't find any package by regex 'linux-headers-4.9.0-9-amd64' I should have kept better notes about how I got my devbox working before, but it's confusing that it would simply stop working. -- Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From dcook at prosentient.com.au Tue Feb 4 01:44:48 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Tue, 4 Feb 2020 11:44:48 +1100 Subject: [Koha-devel] Trouble in setting up kohadevbox on Win10 prof In-Reply-To: <0b4401d5daef$7c342a10$749c7e30$@prosentient.com.au> References: <0b4401d5daef$7c342a10$749c7e30$@prosentient.com.au> Message-ID: <0b4b01d5daf4$4d5948b0$e80bda10$@prosentient.com.au> By the way, everyone, I think I've demonstrated on https://gitlab.com/koha-community/koha-testing-docker/issues/140 how to get koha-testing-docker working again, if you're having any issues with it. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -----Original Message----- From: Koha-devel On Behalf Of dcook at prosentient.com.au Sent: Tuesday, 4 February 2020 11:10 AM To: 'Owen Leonard' ; 'Koha-devel' Subject: Re: [Koha-devel] Trouble in setting up kohadevbox on Win10 prof Damn, sorry to hear that. I have some things to say on that topic, but I'll add them to the Gitlab issue. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -----Original Message----- From: Koha-devel On Behalf Of Owen Leonard Sent: Tuesday, 4 February 2020 12:42 AM To: Koha-devel Subject: Re: [Koha-devel] Trouble in setting up kohadevbox on Win10 prof I used koha-testing-docker on Windows 10 for a while and then it stopped working for me altogether: https://gitlab.com/koha-community/koha-testing-docker/issues/140 > 1. I had to switch the distribution to > https://app.vagrantup.com/digital-port/boxes/debian-stretch64 > because otherwise I was hitting the missing linux-headers for vbox guest additions. I switched back to kohadevbox and got it working after some wrangling, but a few days ago it stopped working too. Now I'm seeing what I think you're seeing too: E: Unable to locate package linux-headers-4.9.0-9-amd64 E: Couldn't find any package by glob 'linux-headers-4.9.0-9-amd64' E: Couldn't find any package by regex 'linux-headers-4.9.0-9-amd64' I should have kept better notes about how I got my devbox working before, but it's confusing that it would simply stop working. -- Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From dcook at prosentient.com.au Tue Feb 4 01:49:10 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Tue, 4 Feb 2020 11:49:10 +1100 Subject: [Koha-devel] Trouble in setting up kohadevbox on Win10 prof In-Reply-To: References: Message-ID: <0b5201d5daf4$e9d8e9c0$bd8abd40$@prosentient.com.au> Yeah, Virtualbox/VMware can't be used at the same time as Hyper-V. Theoretically, the latest Virtualbox can use Hyper-V as a backend, but I couldn't get it to work in practice. Personally, I've completely moved away from Virtualbox and over to Hyper-V. Docker Desktop uses Hyper-V out of the box, and I was able to get GNS3 working with Hyper-V, so I'm pretty content. For what it's worth, Windows users don't have to use "Docker Desktop" and could instead create a Linux VM in Virtualbox and run Docker there instead. Docker Desktop is just more Windows user friendly. (Of course, in the next few months, we might get WSL 2 on Windows 10, which will include a real Linux kernel in a thinner virtualization layer, which would allow people to run Docker on Windows without the full Hyper-V VM, but I digress. I'll be exploring that more once it's officially released.) David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -----Original Message----- From: Koha-devel On Behalf Of Mark Tompsett Sent: Tuesday, 4 February 2020 3:03 AM To: Koha-devel Subject: Re: [Koha-devel] Trouble in setting up kohadevbox on Win10 prof Greetings, My virtualbox didn’t play nice with Hyper-V. And various windows features keep turning it back on, GRRRR! Hit the Windows Key and type “windows features” Hit the Windows Key + W combo to bring up the Windows Settings panel of the Start Screen. Click on Turn Windows features on or off. When the Turn Windows features on or off dialog appears, look for Hyper-V and deselect it. Click OK. Restart your computer when prompted. dism.exe /Online /Disable-Feature:Microsoft-Hyper-V dism.exe /Online /Disable-Feature:Microsoft-Hyper-V /all Restart your computer. bcdedit /set hypervisorlaunchtype off Restart your computer After that, had some issues as my virtualbox, git bash, and vagrant were out of date. So updated those. Then I was lazy: vagrant up It bombed, because of linux-headers something. vagrant ssh sudo apt install linux-headers exit vagrant halt vagrant up It then correctly provisioned. So, while Owen's shared script may be valid, I'm not sure it is necessary to get too detailed. Also, Jonathan Druart made a good point about the SYNC_REPO path being your local windows path, not the one on the VM. GPML, Mark Tompsett _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From martin.renvoize at ptfs-europe.com Tue Feb 4 11:01:58 2020 From: martin.renvoize at ptfs-europe.com (Renvoize, Martin) Date: Tue, 4 Feb 2020 10:01:58 +0000 Subject: [Koha-devel] Bug 18936 - Circulation Rules Ratification Message-ID: Hi All, I just wanted to let you all know that I'll be pushing bug 18936 to the master branch this morning. It's the largest to date of the refactoring bugs and will affect any/all bugs related to the circulation rules handling. It's been thoroughly tested and QA'd, but as a large piece I'm sure there will be a few pain points still buried, so keep an eye out and report any bugs you find. Good luck with any rebases that may be required after this and my apologies, but the end result should give us a much cleaner foundation for circ related enhancements and cleanup in the future. Many thanks to those who have spent many hours coding, testing, refining and qaing this piece, *Martin Renvoize* Development Team Manager Community Release Manager (19.11, 20.05) *Phone:* +44 (0) 1483 378728 *Mobile:* +44 (0) 7725 985 636 *Email:* martin.renvoize at ptfs-europe.com *Fax:* +44 (0) 800 756 6384 www.ptfs-europe.com Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info at ptfs-europe.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Tue Feb 4 13:36:51 2020 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Tue, 4 Feb 2020 09:36:51 -0300 Subject: [Koha-devel] Bug 18936 - Circulation Rules Ratification In-Reply-To: References: Message-ID: Congrats to all involved! El mar., 4 feb. 2020 a las 7:02, Renvoize, Martin (< martin.renvoize at ptfs-europe.com>) escribió: > Hi All, > > I just wanted to let you all know that I'll be pushing bug 18936 to the > master branch this morning. It's the largest to date of the refactoring > bugs and will affect any/all bugs related to the circulation rules handling. > > It's been thoroughly tested and QA'd, but as a large piece I'm sure there > will be a few pain points still buried, so keep an eye out and report any > bugs you find. > > Good luck with any rebases that may be required after this and my > apologies, but the end result should give us a much cleaner foundation for > circ related enhancements and cleanup in the future. > > Many thanks to those who have spent many hours coding, testing, refining > and qaing this piece, > > *Martin Renvoize* > > > > Development Team Manager > > Community Release Manager (19.11, 20.05) > > > *Phone:* +44 (0) 1483 378728 > > *Mobile:* +44 (0) 7725 985 636 > > *Email:* martin.renvoize at ptfs-europe.com > > *Fax:* +44 (0) 800 756 6384 > > > www.ptfs-europe.com > > > > > > > > Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 > > The information contained in this email message may be privileged, > confidential and protected from disclosure. If you are not the intended > recipient, any dissemination, distribution or copying is strictly > prohibited. If you think that you have received this email message in > error, please email the sender at info at ptfs-europe.com > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From julian.maurice at biblibre.com Tue Feb 4 14:25:21 2020 From: julian.maurice at biblibre.com (Julian Maurice) Date: Tue, 4 Feb 2020 14:25:21 +0100 Subject: [Koha-devel] Bug 18936 - Circulation Rules Ratification In-Reply-To: References: Message-ID: Hi Martin, I just discovered this bug and, after reading quickly the bug's comments and commit messages, I didn't find the reason of this big refactoring (why was it needed ? what do we gain ? is it only a rename or is it more than that ?). Is this explained somewhere ? In my opinion changes should be summarized at least in the first commit message, so that people rebasing other patches can have an overview of what changes are needed in their patches. Le 04/02/2020 à 11:01, Renvoize, Martin a écrit : > Hi All, > > I just wanted to let you all know that I'll be pushing bug 18936 to the > master branch this morning. It's the largest to date of the refactoring > bugs and will affect any/all bugs related to the circulation rules handling. > > It's been thoroughly tested and QA'd, but as a large piece I'm sure > there will be a few pain points still buried, so keep an eye out and > report any bugs you find. > > Good luck with any rebases that may be required after this and my > apologies, but the end result should give us a much cleaner foundation > for circ related enhancements and cleanup in the future. > > Many thanks to those who have spent many hours coding, testing, refining > and qaing this piece, > > *Martin Renvoize* > > > > > > Development Team Manager > > Community Release Manager (19.11, 20.05) > > > *Phone:* +44 (0) 1483 378728 > > > > *Mobile:* +44 (0) 7725 985 636 > > *Email:* martin.renvoize at ptfs-europe.com > > > > > *Fax:* +44 (0) 800 756 6384 > > > > > www.ptfs-europe.com > > Registered in the United Kingdom No. 06416372   VAT Reg No. 925 7211 30 > > > The information contained in this email message may be privileged, > confidential and protected from disclosure. If you are not the intended > recipient, any dissemination, distribution or copying is strictly > prohibited. If you think that you have received this email message in > error, please email the sender at info at ptfs-europe.com > > > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -- Julian Maurice BibLibre From julian.maurice at biblibre.com Tue Feb 4 14:55:25 2020 From: julian.maurice at biblibre.com (Julian Maurice) Date: Tue, 4 Feb 2020 14:55:25 +0100 Subject: [Koha-devel] Koha mirror on gitlab.com not updated ? Message-ID: Hi all, It seems the mirror on gitlab is not updated anymore. The last commit on master is 604c7b81 Bug 22816: OPAC detail holdings table should now look a bit better which has been committed in May 2019 Does anyone know why ? -- Julian Maurice BibLibre From tomascohen at gmail.com Tue Feb 4 14:59:46 2020 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Tue, 4 Feb 2020 10:59:46 -0300 Subject: [Koha-devel] Koha mirror on gitlab.com not updated ? In-Reply-To: References: Message-ID: Because of Koha's repo size. El mar., 4 feb. 2020 a las 10:55, Julian Maurice (< julian.maurice at biblibre.com>) escribió: > Hi all, > > It seems the mirror on gitlab is not updated anymore. The last commit on > master is > > 604c7b81 Bug 22816: OPAC detail holdings table should now look a bit better > > which has been committed in May 2019 > > Does anyone know why ? > > -- > Julian Maurice > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From julian.maurice at biblibre.com Tue Feb 4 15:28:11 2020 From: julian.maurice at biblibre.com (Julian Maurice) Date: Tue, 4 Feb 2020 15:28:11 +0100 Subject: [Koha-devel] Koha mirror on gitlab.com not updated ? In-Reply-To: References: Message-ID: Can we do something about that or should we consider the mirror on gitlab to be useless and never use it ? Le 04/02/2020 à 14:59, Tomas Cohen Arazi a écrit : > Because of Koha's repo size. > > El mar., 4 feb. 2020 a las 10:55, Julian Maurice > (>) > escribió: > > Hi all, > > It seems the mirror on gitlab is not updated anymore. The last > commit on > master is > > 604c7b81 Bug 22816: OPAC detail holdings table should now look a bit > better > > which has been committed in May 2019 > > Does anyone know why ? > > -- > Julian Maurice > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > > > > -- > Tomás Cohen Arazi > Theke Solutions (http://theke.io ) > ✆ +54 9351 3513384 > GPG: B2F3C15F -- Julian Maurice BibLibre From agustinmoyano at theke.io Tue Feb 4 16:06:54 2020 From: agustinmoyano at theke.io (Agustin Moyano) Date: Tue, 4 Feb 2020 12:06:54 -0300 Subject: [Koha-devel] Koha mirror on gitlab.com not updated ? In-Reply-To: References: Message-ID: Hi Julian, we could consider mirroring only master, and maybe stable branches. On Tue, Feb 4, 2020 at 11:28 AM Julian Maurice wrote: > Can we do something about that or should we consider the mirror on > gitlab to be useless and never use it ? > > Le 04/02/2020 à 14:59, Tomas Cohen Arazi a écrit : > > Because of Koha's repo size. > > > > El mar., 4 feb. 2020 a las 10:55, Julian Maurice > > (>) > > escribió: > > > > Hi all, > > > > It seems the mirror on gitlab is not updated anymore. The last > > commit on > > master is > > > > 604c7b81 Bug 22816: OPAC detail holdings table should now look a bit > > better > > > > which has been committed in May 2019 > > > > Does anyone know why ? > > > > -- > > Julian Maurice > > BibLibre > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at lists.koha-community.org > > > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ > > git : http://git.koha-community.org/ > > bugs : http://bugs.koha-community.org/ > > > > > > > > -- > > Tomás Cohen Arazi > > Theke Solutions (http://theke.io ) > > ✆ +54 9351 3513384 > > GPG: B2F3C15F > > -- > Julian Maurice > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Tue Feb 4 16:29:49 2020 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Tue, 4 Feb 2020 16:29:49 +0100 Subject: [Koha-devel] Koha mirror on gitlab.com not updated ? In-Reply-To: References: Message-ID: I investigated that issue few months ago, and asked Chris what returned `du -sbh .git` on git.koha-community.org/koha: 2.8G .git So it's really weird that gitlab complains about that size (13GB) At that time (June 2019) the gitlab interface says "17Go, 7 over the limit of 10." So numbers look quite inconsistent. See also the issue I opened on their bug tracker: https://gitlab.com/gitlab-com/support-forum/issues/4590 Le mar. 4 févr. 2020 à 15:28, Julian Maurice a écrit : > > Can we do something about that or should we consider the mirror on > gitlab to be useless and never use it ? > > Le 04/02/2020 à 14:59, Tomas Cohen Arazi a écrit : > > Because of Koha's repo size. > > > > El mar., 4 feb. 2020 a las 10:55, Julian Maurice > > (>) > > escribió: > > > > Hi all, > > > > It seems the mirror on gitlab is not updated anymore. The last > > commit on > > master is > > > > 604c7b81 Bug 22816: OPAC detail holdings table should now look a bit > > better > > > > which has been committed in May 2019 > > > > Does anyone know why ? > > > > -- > > Julian Maurice > > BibLibre > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at lists.koha-community.org > > > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ > > git : http://git.koha-community.org/ > > bugs : http://bugs.koha-community.org/ > > > > > > > > -- > > Tomás Cohen Arazi > > Theke Solutions (http://theke.io ) > > ✆ +54 9351 3513384 > > GPG: B2F3C15F > > -- > Julian Maurice > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ From jonathan.druart at bugs.koha-community.org Tue Feb 4 16:40:55 2020 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Tue, 4 Feb 2020 16:40:55 +0100 Subject: [Koha-devel] Bug 18936 - Circulation Rules Ratification In-Reply-To: References: Message-ID: Bug 18936 is the groundwork for bug 15522 (revamp issuing rules interface). Everybody should have heard about it as the mailing list contains several occurrences of this work: ask for help, signoff/QA, as well as the different call for the proposal, starting 4 years ago. Bug 18936 does not bring anything to the end-user, but basically you just need to keep in mind that: - the issuingrules table does not longer exist (!) - rules are now in the circulation_rules, which has the following structure: branchcode, categorycode, itemtype, rule_name, rule_value (so 1 row per rule) - you should call Koha::CirculationRules->set_rule (single) or set_rules (multiple) to define/set circulation rules - the rebase was painful and I apologized in advance for the issues I left behind :) - bug 15522 is on its way, and it would be really useful to get more testing on it! Cheers Le mar. 4 févr. 2020 à 14:25, Julian Maurice a écrit : > > Hi Martin, > > I just discovered this bug and, after reading quickly the bug's comments > and commit messages, I didn't find the reason of this big refactoring > (why was it needed ? what do we gain ? is it only a rename or is it more > than that ?). Is this explained somewhere ? > > In my opinion changes should be summarized at least in the first commit > message, so that people rebasing other patches can have an overview of > what changes are needed in their patches. > > Le 04/02/2020 à 11:01, Renvoize, Martin a écrit : > > Hi All, > > > > I just wanted to let you all know that I'll be pushing bug 18936 to the > > master branch this morning. It's the largest to date of the refactoring > > bugs and will affect any/all bugs related to the circulation rules handling. > > > > It's been thoroughly tested and QA'd, but as a large piece I'm sure > > there will be a few pain points still buried, so keep an eye out and > > report any bugs you find. > > > > Good luck with any rebases that may be required after this and my > > apologies, but the end result should give us a much cleaner foundation > > for circ related enhancements and cleanup in the future. > > > > Many thanks to those who have spent many hours coding, testing, refining > > and qaing this piece, > > > > *Martin Renvoize* > > > > > > > > > > > > Development Team Manager > > > > Community Release Manager (19.11, 20.05) > > > > > > *Phone:* +44 (0) 1483 378728 > > > > > > > > *Mobile:* +44 (0) 7725 985 636 > > > > *Email:* martin.renvoize at ptfs-europe.com > > > > > > > > > > *Fax:* +44 (0) 800 756 6384 > > > > > > > > > > www.ptfs-europe.com > > > > Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 > > > > > > The information contained in this email message may be privileged, > > confidential and protected from disclosure. If you are not the intended > > recipient, any dissemination, distribution or copying is strictly > > prohibited. If you think that you have received this email message in > > error, please email the sender at info at ptfs-europe.com > > > > > > > > > > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at lists.koha-community.org > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ > > git : http://git.koha-community.org/ > > bugs : http://bugs.koha-community.org/ > > > > -- > Julian Maurice > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ From julian.maurice at biblibre.com Tue Feb 4 16:46:31 2020 From: julian.maurice at biblibre.com (Julian Maurice) Date: Tue, 4 Feb 2020 16:46:31 +0100 Subject: [Koha-devel] Koha mirror on gitlab.com not updated ? In-Reply-To: References: Message-ID: 7 months without an answer from GitLab support... :/ Have you considered moving to github instead ? (github has a hard limit of 100GB per repository) Le 04/02/2020 à 16:29, Jonathan Druart a écrit : > I investigated that issue few months ago, and asked Chris what > returned `du -sbh .git` on git.koha-community.org/koha: 2.8G .git > So it's really weird that gitlab complains about that size (13GB) > At that time (June 2019) the gitlab interface says "17Go, 7 over the > limit of 10." > So numbers look quite inconsistent. > > See also the issue I opened on their bug tracker: > https://gitlab.com/gitlab-com/support-forum/issues/4590 > > > > Le mar. 4 févr. 2020 à 15:28, Julian Maurice > a écrit : >> >> Can we do something about that or should we consider the mirror on >> gitlab to be useless and never use it ? >> >> Le 04/02/2020 à 14:59, Tomas Cohen Arazi a écrit : >>> Because of Koha's repo size. >>> >>> El mar., 4 feb. 2020 a las 10:55, Julian Maurice >>> (>) >>> escribió: >>> >>> Hi all, >>> >>> It seems the mirror on gitlab is not updated anymore. The last >>> commit on >>> master is >>> >>> 604c7b81 Bug 22816: OPAC detail holdings table should now look a bit >>> better >>> >>> which has been committed in May 2019 >>> >>> Does anyone know why ? >>> >>> -- >>> Julian Maurice >>> BibLibre >>> _______________________________________________ >>> Koha-devel mailing list >>> Koha-devel at lists.koha-community.org >>> >>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>> website : http://www.koha-community.org/ >>> git : http://git.koha-community.org/ >>> bugs : http://bugs.koha-community.org/ >>> >>> >>> >>> -- >>> Tomás Cohen Arazi >>> Theke Solutions (http://theke.io ) >>> ✆ +54 9351 3513384 >>> GPG: B2F3C15F >> >> -- >> Julian Maurice >> BibLibre >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ -- Julian Maurice BibLibre From julian.maurice at biblibre.com Tue Feb 4 17:58:23 2020 From: julian.maurice at biblibre.com (Julian Maurice) Date: Tue, 4 Feb 2020 17:58:23 +0100 Subject: [Koha-devel] Bug 18936 - Circulation Rules Ratification In-Reply-To: References: Message-ID: <05f2d11b-6f62-3461-624a-406baaf8c10d@biblibre.com> Thanks for the clarification, but my comment was more about "how people could find this information" rather than "give me this information". Currently it's not in the bug, not in commit messages, not in any kind of documentation. During the last developer irc meeting it was decided to reinforce good commit message guideline, and I think that could have been useful here. Specifically the "why" part is missing and the "what" part could have been more verbose. Apart from this particular bug, I think everyone would benefit from a "developer changelog" where all this kind of changes (database renames, subroutines removals, ...) would be written. Just my 2 cents... PS: Not everyone has time to look at all the bugs discussed on the mailing list. Please don't make me feel guilty about it :) Le 04/02/2020 à 16:40, Jonathan Druart a écrit : > Bug 18936 is the groundwork for bug 15522 (revamp issuing rules interface). > > Everybody should have heard about it as the mailing list contains > several occurrences of this work: ask for help, signoff/QA, as well as > the different call for the proposal, starting 4 years ago. > > Bug 18936 does not bring anything to the end-user, but basically you > just need to keep in mind that: > - the issuingrules table does not longer exist (!) > - rules are now in the circulation_rules, which has the following > structure: branchcode, categorycode, itemtype, rule_name, rule_value > (so 1 row per rule) > - you should call Koha::CirculationRules->set_rule (single) or > set_rules (multiple) to define/set circulation rules > - the rebase was painful and I apologized in advance for the issues I > left behind :) > - bug 15522 is on its way, and it would be really useful to get more > testing on it! > > Cheers > > > Le mar. 4 févr. 2020 à 14:25, Julian Maurice > a écrit : >> >> Hi Martin, >> >> I just discovered this bug and, after reading quickly the bug's comments >> and commit messages, I didn't find the reason of this big refactoring >> (why was it needed ? what do we gain ? is it only a rename or is it more >> than that ?). Is this explained somewhere ? >> >> In my opinion changes should be summarized at least in the first commit >> message, so that people rebasing other patches can have an overview of >> what changes are needed in their patches. >> >> Le 04/02/2020 à 11:01, Renvoize, Martin a écrit : >>> Hi All, >>> >>> I just wanted to let you all know that I'll be pushing bug 18936 to the >>> master branch this morning. It's the largest to date of the refactoring >>> bugs and will affect any/all bugs related to the circulation rules handling. >>> >>> It's been thoroughly tested and QA'd, but as a large piece I'm sure >>> there will be a few pain points still buried, so keep an eye out and >>> report any bugs you find. >>> >>> Good luck with any rebases that may be required after this and my >>> apologies, but the end result should give us a much cleaner foundation >>> for circ related enhancements and cleanup in the future. >>> >>> Many thanks to those who have spent many hours coding, testing, refining >>> and qaing this piece, >>> >>> *Martin Renvoize* >>> >>> >>> >>> >>> >>> Development Team Manager >>> >>> Community Release Manager (19.11, 20.05) >>> >>> >>> *Phone:* +44 (0) 1483 378728 >>> >>> >>> >>> *Mobile:* +44 (0) 7725 985 636 >>> >>> *Email:* martin.renvoize at ptfs-europe.com >>> >>> >>> >>> >>> *Fax:* +44 (0) 800 756 6384 >>> >>> >>> >>> >>> www.ptfs-europe.com >>> >>> Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 >>> >>> >>> The information contained in this email message may be privileged, >>> confidential and protected from disclosure. If you are not the intended >>> recipient, any dissemination, distribution or copying is strictly >>> prohibited. If you think that you have received this email message in >>> error, please email the sender at info at ptfs-europe.com >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Koha-devel mailing list >>> Koha-devel at lists.koha-community.org >>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>> website : http://www.koha-community.org/ >>> git : http://git.koha-community.org/ >>> bugs : http://bugs.koha-community.org/ >>> >> >> -- >> Julian Maurice >> BibLibre >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ -- Julian Maurice BibLibre From dcook at prosentient.com.au Wed Feb 5 01:36:47 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Wed, 5 Feb 2020 11:36:47 +1100 Subject: [Koha-devel] Koha mirror on gitlab.com not updated ? In-Reply-To: References: Message-ID: <0bfc01d5dbbc$5984d5f0$0c8e81d0$@prosentient.com.au> I know some folk at Gitlab. Let me see if I can be a squeaky wheel to get us some oil. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -----Original Message----- From: Koha-devel On Behalf Of Julian Maurice Sent: Wednesday, 5 February 2020 2:47 AM To: Jonathan Druart Cc: koha-devel Subject: Re: [Koha-devel] Koha mirror on gitlab.com not updated ? 7 months without an answer from GitLab support... :/ Have you considered moving to github instead ? (github has a hard limit of 100GB per repository) Le 04/02/2020 à 16:29, Jonathan Druart a écrit : > I investigated that issue few months ago, and asked Chris what > returned `du -sbh .git` on git.koha-community.org/koha: 2.8G .git > So it's really weird that gitlab complains about that size (13GB) At > that time (June 2019) the gitlab interface says "17Go, 7 over the > limit of 10." > So numbers look quite inconsistent. > > See also the issue I opened on their bug tracker: > https://gitlab.com/gitlab-com/support-forum/issues/4590 > > > > Le mar. 4 févr. 2020 à 15:28, Julian Maurice > a écrit : >> >> Can we do something about that or should we consider the mirror on >> gitlab to be useless and never use it ? >> >> Le 04/02/2020 à 14:59, Tomas Cohen Arazi a écrit : >>> Because of Koha's repo size. >>> >>> El mar., 4 feb. 2020 a las 10:55, Julian Maurice >>> (>) >>> escribió: >>> >>> Hi all, >>> >>> It seems the mirror on gitlab is not updated anymore. The last >>> commit on >>> master is >>> >>> 604c7b81 Bug 22816: OPAC detail holdings table should now look a bit >>> better >>> >>> which has been committed in May 2019 >>> >>> Does anyone know why ? >>> >>> -- >>> Julian Maurice >>> BibLibre >>> _______________________________________________ >>> Koha-devel mailing list >>> Koha-devel at lists.koha-community.org >>> >>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>> website : http://www.koha-community.org/ >>> git : http://git.koha-community.org/ >>> bugs : http://bugs.koha-community.org/ >>> >>> >>> >>> -- >>> Tomás Cohen Arazi >>> Theke Solutions (http://theke.io ) ✆ +54 9351 >>> 3513384 >>> GPG: B2F3C15F >> >> -- >> Julian Maurice >> BibLibre >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ git : >> http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -- Julian Maurice BibLibre _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From joonas.kylmala at helsinki.fi Wed Feb 5 09:47:23 2020 From: joonas.kylmala at helsinki.fi (=?UTF-8?Q?Joonas_Kylm=c3=a4l=c3=a4?=) Date: Wed, 5 Feb 2020 10:47:23 +0200 Subject: [Koha-devel] Bug 18936 - Circulation Rules Ratification In-Reply-To: <05f2d11b-6f62-3461-624a-406baaf8c10d@biblibre.com> References: <05f2d11b-6f62-3461-624a-406baaf8c10d@biblibre.com> Message-ID: Hi, if you are still interested to know the why part, it is explained in the wiki: . I definitely agree it should have been in the commits too but I got maybe too lax as a QA person since we had so many regressions fixed already (took around 2 weeks to do the QA) the earliest patches were send and revised already 2.5 years ago so this has been a long process but I guess not a real excuse either. As for the developer changelog, I'm fine with reading just the git history but for this to work ideally I still think the follow-ups from the patch author itself are bad and we need to be strict about enforcing good commit messages! On 04/02/2020 18:58, Julian Maurice wrote: > Thanks for the clarification, but my comment was more about "how people > could find this information" rather than "give me this information". > Currently it's not in the bug, not in commit messages, not in any kind > of documentation. > > During the last developer irc meeting it was decided to reinforce good > commit message guideline, and I think that could have been useful here. > Specifically the "why" part is missing and the "what" part could have > been more verbose. > > Apart from this particular bug, I think everyone would benefit from a > "developer changelog" where all this kind of changes (database renames, > subroutines removals, ...) would be written. > > Just my 2 cents... > > PS: Not everyone has time to look at all the bugs discussed on the > mailing list. Please don't make me feel guilty about it :) From jonathan.druart at bugs.koha-community.org Wed Feb 5 10:00:59 2020 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Wed, 5 Feb 2020 10:00:59 +0100 Subject: [Koha-devel] Koha mirror on gitlab.com not updated ? In-Reply-To: References: Message-ID: > Have you considered moving to github instead ? (github has a hard limit > of 100GB per repository) We moved from github to gitlab a couple of years ago ;) > Le 04/02/2020 à 16:29, Jonathan Druart a écrit : > > I investigated that issue few months ago, and asked Chris what > > returned `du -sbh .git` on git.koha-community.org/koha: 2.8G .git > > So it's really weird that gitlab complains about that size (13GB) > > At that time (June 2019) the gitlab interface says "17Go, 7 over the > > limit of 10." > > So numbers look quite inconsistent. > > > > See also the issue I opened on their bug tracker: > > https://gitlab.com/gitlab-com/support-forum/issues/4590 > > > > > > > > Le mar. 4 févr. 2020 à 15:28, Julian Maurice > > a écrit : > >> > >> Can we do something about that or should we consider the mirror on > >> gitlab to be useless and never use it ? > >> > >> Le 04/02/2020 à 14:59, Tomas Cohen Arazi a écrit : > >>> Because of Koha's repo size. > >>> > >>> El mar., 4 feb. 2020 a las 10:55, Julian Maurice > >>> (>) > >>> escribió: > >>> > >>> Hi all, > >>> > >>> It seems the mirror on gitlab is not updated anymore. The last > >>> commit on > >>> master is > >>> > >>> 604c7b81 Bug 22816: OPAC detail holdings table should now look a bit > >>> better > >>> > >>> which has been committed in May 2019 > >>> > >>> Does anyone know why ? > >>> > >>> -- > >>> Julian Maurice > >>> BibLibre > >>> _______________________________________________ > >>> Koha-devel mailing list > >>> Koha-devel at lists.koha-community.org > >>> > >>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > >>> website : http://www.koha-community.org/ > >>> git : http://git.koha-community.org/ > >>> bugs : http://bugs.koha-community.org/ > >>> > >>> > >>> > >>> -- > >>> Tomás Cohen Arazi > >>> Theke Solutions (http://theke.io ) > >>> ✆ +54 9351 3513384 > >>> GPG: B2F3C15F > >> > >> -- > >> Julian Maurice > >> BibLibre > >> _______________________________________________ > >> Koha-devel mailing list > >> Koha-devel at lists.koha-community.org > >> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > >> website : http://www.koha-community.org/ > >> git : http://git.koha-community.org/ > >> bugs : http://bugs.koha-community.org/ > > -- > Julian Maurice > BibLibre From jonathan.druart at bugs.koha-community.org Wed Feb 5 10:11:17 2020 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Wed, 5 Feb 2020 10:11:17 +0100 Subject: [Koha-devel] Bug 18936 - Circulation Rules Ratification In-Reply-To: <05f2d11b-6f62-3461-624a-406baaf8c10d@biblibre.com> References: <05f2d11b-6f62-3461-624a-406baaf8c10d@biblibre.com> Message-ID: I am going to support any good ideas from bug 22890 (Add a chronological changelog). Still waiting for continuing the discussion there however. What can we do to move it forward? Le mar. 4 févr. 2020 à 17:58, Julian Maurice a écrit : > > Thanks for the clarification, but my comment was more about "how people > could find this information" rather than "give me this information". > Currently it's not in the bug, not in commit messages, not in any kind > of documentation. > > During the last developer irc meeting it was decided to reinforce good > commit message guideline, and I think that could have been useful here. > Specifically the "why" part is missing and the "what" part could have > been more verbose. > > Apart from this particular bug, I think everyone would benefit from a > "developer changelog" where all this kind of changes (database renames, > subroutines removals, ...) would be written. > > Just my 2 cents... > > PS: Not everyone has time to look at all the bugs discussed on the > mailing list. Please don't make me feel guilty about it :) > > Le 04/02/2020 à 16:40, Jonathan Druart a écrit : > > Bug 18936 is the groundwork for bug 15522 (revamp issuing rules interface). > > > > Everybody should have heard about it as the mailing list contains > > several occurrences of this work: ask for help, signoff/QA, as well as > > the different call for the proposal, starting 4 years ago. > > > > Bug 18936 does not bring anything to the end-user, but basically you > > just need to keep in mind that: > > - the issuingrules table does not longer exist (!) > > - rules are now in the circulation_rules, which has the following > > structure: branchcode, categorycode, itemtype, rule_name, rule_value > > (so 1 row per rule) > > - you should call Koha::CirculationRules->set_rule (single) or > > set_rules (multiple) to define/set circulation rules > > - the rebase was painful and I apologized in advance for the issues I > > left behind :) > > - bug 15522 is on its way, and it would be really useful to get more > > testing on it! > > > > Cheers > > > > > > Le mar. 4 févr. 2020 à 14:25, Julian Maurice > > a écrit : > >> > >> Hi Martin, > >> > >> I just discovered this bug and, after reading quickly the bug's comments > >> and commit messages, I didn't find the reason of this big refactoring > >> (why was it needed ? what do we gain ? is it only a rename or is it more > >> than that ?). Is this explained somewhere ? > >> > >> In my opinion changes should be summarized at least in the first commit > >> message, so that people rebasing other patches can have an overview of > >> what changes are needed in their patches. > >> > >> Le 04/02/2020 à 11:01, Renvoize, Martin a écrit : > >>> Hi All, > >>> > >>> I just wanted to let you all know that I'll be pushing bug 18936 to the > >>> master branch this morning. It's the largest to date of the refactoring > >>> bugs and will affect any/all bugs related to the circulation rules handling. > >>> > >>> It's been thoroughly tested and QA'd, but as a large piece I'm sure > >>> there will be a few pain points still buried, so keep an eye out and > >>> report any bugs you find. > >>> > >>> Good luck with any rebases that may be required after this and my > >>> apologies, but the end result should give us a much cleaner foundation > >>> for circ related enhancements and cleanup in the future. > >>> > >>> Many thanks to those who have spent many hours coding, testing, refining > >>> and qaing this piece, > >>> > >>> *Martin Renvoize* > >>> > >>> > >>> > >>> > >>> > >>> Development Team Manager > >>> > >>> Community Release Manager (19.11, 20.05) > >>> > >>> > >>> *Phone:* +44 (0) 1483 378728 > >>> > >>> > >>> > >>> *Mobile:* +44 (0) 7725 985 636 > >>> > >>> *Email:* martin.renvoize at ptfs-europe.com > >>> > >>> > >>> > >>> > >>> *Fax:* +44 (0) 800 756 6384 > >>> > >>> > >>> > >>> > >>> www.ptfs-europe.com > >>> > >>> Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 > >>> > >>> > >>> The information contained in this email message may be privileged, > >>> confidential and protected from disclosure. If you are not the intended > >>> recipient, any dissemination, distribution or copying is strictly > >>> prohibited. If you think that you have received this email message in > >>> error, please email the sender at info at ptfs-europe.com > >>> > >>> > >>> > >>> > >>> > >>> _______________________________________________ > >>> Koha-devel mailing list > >>> Koha-devel at lists.koha-community.org > >>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > >>> website : http://www.koha-community.org/ > >>> git : http://git.koha-community.org/ > >>> bugs : http://bugs.koha-community.org/ > >>> > >> > >> -- > >> Julian Maurice > >> BibLibre > >> _______________________________________________ > >> Koha-devel mailing list > >> Koha-devel at lists.koha-community.org > >> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > >> website : http://www.koha-community.org/ > >> git : http://git.koha-community.org/ > >> bugs : http://bugs.koha-community.org/ > > -- > Julian Maurice > BibLibre From julian.maurice at biblibre.com Wed Feb 5 15:47:12 2020 From: julian.maurice at biblibre.com (Julian Maurice) Date: Wed, 5 Feb 2020 15:47:12 +0100 Subject: [Koha-devel] Koha mirror on gitlab.com not updated ? In-Reply-To: References: Message-ID: <76195246-84f8-cbbd-9c85-f630f30de0f5@biblibre.com> I know there is a mirror on github but the koha-community organization there has only 4 repositories, including one which points to gitlab.com (kohadocs), and another that is not directly related to koha (perlweb). If we compare to gitlab.com where there are 17 repositories, I think we cannot say that we "moved" to github. So, the situation is a little weird as almost all repositories are on gitlab, except for the main repository which is not updated correctly, so people have to go elsewhere (github or git.koha-community.org) to get koha Hopefully gitlab will fix the issue. But what if they don't ? :/ Le 05/02/2020 à 10:00, Jonathan Druart a écrit : >> Have you considered moving to github instead ? (github has a hard limit >> of 100GB per repository) > > We moved from github to gitlab a couple of years ago ;) > > >> Le 04/02/2020 à 16:29, Jonathan Druart a écrit : >>> I investigated that issue few months ago, and asked Chris what >>> returned `du -sbh .git` on git.koha-community.org/koha: 2.8G .git >>> So it's really weird that gitlab complains about that size (13GB) >>> At that time (June 2019) the gitlab interface says "17Go, 7 over the >>> limit of 10." >>> So numbers look quite inconsistent. >>> >>> See also the issue I opened on their bug tracker: >>> https://gitlab.com/gitlab-com/support-forum/issues/4590 >>> >>> >>> >>> Le mar. 4 févr. 2020 à 15:28, Julian Maurice >>> a écrit : >>>> >>>> Can we do something about that or should we consider the mirror on >>>> gitlab to be useless and never use it ? >>>> >>>> Le 04/02/2020 à 14:59, Tomas Cohen Arazi a écrit : >>>>> Because of Koha's repo size. >>>>> >>>>> El mar., 4 feb. 2020 a las 10:55, Julian Maurice >>>>> (>) >>>>> escribió: >>>>> >>>>> Hi all, >>>>> >>>>> It seems the mirror on gitlab is not updated anymore. The last >>>>> commit on >>>>> master is >>>>> >>>>> 604c7b81 Bug 22816: OPAC detail holdings table should now look a bit >>>>> better >>>>> >>>>> which has been committed in May 2019 >>>>> >>>>> Does anyone know why ? >>>>> >>>>> -- >>>>> Julian Maurice >>>>> BibLibre >>>>> _______________________________________________ >>>>> Koha-devel mailing list >>>>> Koha-devel at lists.koha-community.org >>>>> >>>>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>>>> website : http://www.koha-community.org/ >>>>> git : http://git.koha-community.org/ >>>>> bugs : http://bugs.koha-community.org/ >>>>> >>>>> >>>>> >>>>> -- >>>>> Tomás Cohen Arazi >>>>> Theke Solutions (http://theke.io ) >>>>> ✆ +54 9351 3513384 >>>>> GPG: B2F3C15F >>>> >>>> -- >>>> Julian Maurice >>>> BibLibre >>>> _______________________________________________ >>>> Koha-devel mailing list >>>> Koha-devel at lists.koha-community.org >>>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>>> website : http://www.koha-community.org/ >>>> git : http://git.koha-community.org/ >>>> bugs : http://bugs.koha-community.org/ >> >> -- >> Julian Maurice >> BibLibre -- Julian Maurice BibLibre From julian.maurice at biblibre.com Wed Feb 5 17:17:04 2020 From: julian.maurice at biblibre.com (Julian Maurice) Date: Wed, 5 Feb 2020 17:17:04 +0100 Subject: [Koha-devel] Bug 18936 - Circulation Rules Ratification In-Reply-To: References: <05f2d11b-6f62-3461-624a-406baaf8c10d@biblibre.com> Message-ID: I can easily understand why the commit messages were not revised, and I certainly wouldn't want to be the person that delay such an important patchset because of the commit messages. The problem with commit messages is that they cannot be changed/improved after the commits have been pushed. And as you said, follow-ups often pollute the history. Also, it may be easier to enforce a rule like "you have to write one line in ChangeLog" than a rule like "you have to write a good commit message" because good and bad are really subjective. And if the line in ChangeLog is not good enough, it can still be improved later, after the commits are pushed. Maybe we can continue this discussion on bug 22890, as Jonathan suggested Le 05/02/2020 à 09:47, Joonas Kylmälä a écrit : > Hi, > > if you are still interested to know the why part, it is explained in the > wiki: > . > I definitely agree it should have been in the commits too but I got > maybe too lax as a QA person since we had so many regressions fixed > already (took around 2 weeks to do the QA) the earliest patches were > send and revised already 2.5 years ago so this has been a long process > but I guess not a real excuse either. > > As for the developer changelog, I'm fine with reading just the git > history but for this to work ideally I still think the follow-ups from > the patch author itself are bad and we need to be strict about enforcing > good commit messages! > > On 04/02/2020 18:58, Julian Maurice wrote: >> Thanks for the clarification, but my comment was more about "how people >> could find this information" rather than "give me this information". >> Currently it's not in the bug, not in commit messages, not in any kind >> of documentation. >> >> During the last developer irc meeting it was decided to reinforce good >> commit message guideline, and I think that could have been useful here. >> Specifically the "why" part is missing and the "what" part could have >> been more verbose. >> >> Apart from this particular bug, I think everyone would benefit from a >> "developer changelog" where all this kind of changes (database renames, >> subroutines removals, ...) would be written. >> >> Just my 2 cents... >> >> PS: Not everyone has time to look at all the bugs discussed on the >> mailing list. Please don't make me feel guilty about it :) -- Julian Maurice BibLibre From martin.renvoize at ptfs-europe.com Wed Feb 5 19:17:14 2020 From: martin.renvoize at ptfs-europe.com (Renvoize, Martin) Date: Wed, 5 Feb 2020 18:17:14 +0000 Subject: [Koha-devel] Koha mirror on gitlab.com not updated ? In-Reply-To: <76195246-84f8-cbbd-9c85-f630f30de0f5@biblibre.com> References: <76195246-84f8-cbbd-9c85-f630f30de0f5@biblibre.com> Message-ID: Our repo is certainly a bit on the big side.. but I'm also disappointed in the lack of response from gitlab. Perhaps we could clarify the issue title a little.. Its not clear from the title that we believe gitlab is estimating the size wrongly On Wed, 5 Feb 2020, 2:47 pm Julian Maurice, wrote: > I know there is a mirror on github but the koha-community organization > there has only 4 repositories, including one which points to gitlab.com > (kohadocs), and another that is not directly related to koha (perlweb). > If we compare to gitlab.com where there are 17 repositories, I think we > cannot say that we "moved" to github. > > So, the situation is a little weird as almost all repositories are on > gitlab, except for the main repository which is not updated correctly, > so people have to go elsewhere (github or git.koha-community.org) to get > koha > > Hopefully gitlab will fix the issue. But what if they don't ? :/ > > Le 05/02/2020 à 10:00, Jonathan Druart a écrit : > >> Have you considered moving to github instead ? (github has a hard limit > >> of 100GB per repository) > > > > We moved from github to gitlab a couple of years ago ;) > > > > > >> Le 04/02/2020 à 16:29, Jonathan Druart a écrit : > >>> I investigated that issue few months ago, and asked Chris what > >>> returned `du -sbh .git` on git.koha-community.org/koha: 2.8G .git > >>> So it's really weird that gitlab complains about that size (13GB) > >>> At that time (June 2019) the gitlab interface says "17Go, 7 over the > >>> limit of 10." > >>> So numbers look quite inconsistent. > >>> > >>> See also the issue I opened on their bug tracker: > >>> https://gitlab.com/gitlab-com/support-forum/issues/4590 > >>> > >>> > >>> > >>> Le mar. 4 févr. 2020 à 15:28, Julian Maurice > >>> a écrit : > >>>> > >>>> Can we do something about that or should we consider the mirror on > >>>> gitlab to be useless and never use it ? > >>>> > >>>> Le 04/02/2020 à 14:59, Tomas Cohen Arazi a écrit : > >>>>> Because of Koha's repo size. > >>>>> > >>>>> El mar., 4 feb. 2020 a las 10:55, Julian Maurice > >>>>> (>) > >>>>> escribió: > >>>>> > >>>>> Hi all, > >>>>> > >>>>> It seems the mirror on gitlab is not updated anymore. The last > >>>>> commit on > >>>>> master is > >>>>> > >>>>> 604c7b81 Bug 22816: OPAC detail holdings table should now look > a bit > >>>>> better > >>>>> > >>>>> which has been committed in May 2019 > >>>>> > >>>>> Does anyone know why ? > >>>>> > >>>>> -- > >>>>> Julian Maurice > >>>>> BibLibre > >>>>> _______________________________________________ > >>>>> Koha-devel mailing list > >>>>> Koha-devel at lists.koha-community.org > >>>>> > >>>>> > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > >>>>> website : http://www.koha-community.org/ > >>>>> git : http://git.koha-community.org/ > >>>>> bugs : http://bugs.koha-community.org/ > >>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> Tomás Cohen Arazi > >>>>> Theke Solutions (http://theke.io ) > >>>>> ✆ +54 9351 3513384 > >>>>> GPG: B2F3C15F > >>>> > >>>> -- > >>>> Julian Maurice > >>>> BibLibre > >>>> _______________________________________________ > >>>> Koha-devel mailing list > >>>> Koha-devel at lists.koha-community.org > >>>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > >>>> website : http://www.koha-community.org/ > >>>> git : http://git.koha-community.org/ > >>>> bugs : http://bugs.koha-community.org/ > >> > >> -- > >> Julian Maurice > >> BibLibre > > -- > Julian Maurice > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Thu Feb 6 03:40:30 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Thu, 6 Feb 2020 13:40:30 +1100 Subject: [Koha-devel] Koha mirror on gitlab.com not updated ? In-Reply-To: References: <76195246-84f8-cbbd-9c85-f630f30de0f5@biblibre.com> Message-ID: <0cd401d5dc96$cc1c27a0$645476e0$@prosentient.com.au> I’ve been in touch with someone at Gitlab, and they pointed out that https://gitlab.com/gitlab-com/support-forum/issues/4590 is just a forum rather than a bug tracker per se. That said, I see Gitlab employees commenting on other “support-forum” issues like https://gitlab.com/gitlab-com/support-forum/issues/5165. The information at https://about.gitlab.com/support/#differences-between-support-tickets-and-gitlab-issues is a bit confusing, as it seems to suggest free users can’t open tickets, but https://support.gitlab.com/hc/en-us has an option for free users to open tickets. I was also told that it was fine for free users to open tickets, although there is no SLA governing response times. I suggest that we submit a new support ticket via https://support.gitlab.com/hc/en-us. If the number is shared with me, I’d be happy to try contacting Gitlab folk via side channels to see if they can prioritize it a bit. Judging from https://docs.gitlab.com/ee/user/project/repository/reducing_the_repo_size_using_git.html (and some things I’ve heard), it sounds like Gitlab might need to do cleanup work on their end. I don’t think rewriting history is the answer, but maybe they need to do some git garbage collection or do something else to “clean up its own internal state”. That all being said, while we might solve this problem this once, I imagine it might happen again, so what would our long-term plan be? Is there a reason we use Gitlab.com instead of self-hosting Gitlab? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Koha-devel On Behalf Of Renvoize, Martin Sent: Thursday, 6 February 2020 5:17 AM To: Julian Maurice Cc: koha-devel Subject: Re: [Koha-devel] Koha mirror on gitlab.com not updated ? Our repo is certainly a bit on the big side.. but I'm also disappointed in the lack of response from gitlab. Perhaps we could clarify the issue title a little.. Its not clear from the title that we believe gitlab is estimating the size wrongly On Wed, 5 Feb 2020, 2:47 pm Julian Maurice, > wrote: I know there is a mirror on github but the koha-community organization there has only 4 repositories, including one which points to gitlab.com (kohadocs), and another that is not directly related to koha (perlweb). If we compare to gitlab.com where there are 17 repositories, I think we cannot say that we "moved" to github. So, the situation is a little weird as almost all repositories are on gitlab, except for the main repository which is not updated correctly, so people have to go elsewhere (github or git.koha-community.org ) to get koha Hopefully gitlab will fix the issue. But what if they don't ? :/ Le 05/02/2020 à 10:00, Jonathan Druart a écrit : >> Have you considered moving to github instead ? (github has a hard limit >> of 100GB per repository) > > We moved from github to gitlab a couple of years ago ;) > > >> Le 04/02/2020 à 16:29, Jonathan Druart a écrit : >>> I investigated that issue few months ago, and asked Chris what >>> returned `du -sbh .git` on git.koha-community.org/koha : 2.8G .git >>> So it's really weird that gitlab complains about that size (13GB) >>> At that time (June 2019) the gitlab interface says "17Go, 7 over the >>> limit of 10." >>> So numbers look quite inconsistent. >>> >>> See also the issue I opened on their bug tracker: >>> https://gitlab.com/gitlab-com/support-forum/issues/4590 >>> >>> >>> >>> Le mar. 4 févr. 2020 à 15:28, Julian Maurice >>> > a écrit : >>>> >>>> Can we do something about that or should we consider the mirror on >>>> gitlab to be useless and never use it ? >>>> >>>> Le 04/02/2020 à 14:59, Tomas Cohen Arazi a écrit : >>>>> Because of Koha's repo size. >>>>> >>>>> El mar., 4 feb. 2020 a las 10:55, Julian Maurice >>>>> ( >>) >>>>> escribió: >>>>> >>>>> Hi all, >>>>> >>>>> It seems the mirror on gitlab is not updated anymore. The last >>>>> commit on >>>>> master is >>>>> >>>>> 604c7b81 Bug 22816: OPAC detail holdings table should now look a bit >>>>> better >>>>> >>>>> which has been committed in May 2019 >>>>> >>>>> Does anyone know why ? >>>>> >>>>> -- >>>>> Julian Maurice >>>>> BibLibre >>>>> _______________________________________________ >>>>> Koha-devel mailing list >>>>> Koha-devel at lists.koha-community.org >>>>> > >>>>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>>>> website : http://www.koha-community.org/ >>>>> git : http://git.koha-community.org/ >>>>> bugs : http://bugs.koha-community.org/ >>>>> >>>>> >>>>> >>>>> -- >>>>> Tomás Cohen Arazi >>>>> Theke Solutions (http://theke.io ) >>>>> ✆ +54 9351 3513384 >>>>> GPG: B2F3C15F >>>> >>>> -- >>>> Julian Maurice >>>> BibLibre >>>> _______________________________________________ >>>> Koha-devel mailing list >>>> Koha-devel at lists.koha-community.org >>>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>>> website : http://www.koha-community.org/ >>>> git : http://git.koha-community.org/ >>>> bugs : http://bugs.koha-community.org/ >> >> -- >> Julian Maurice >> BibLibre -- Julian Maurice BibLibre _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From dcook at prosentient.com.au Thu Feb 6 06:15:59 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Thu, 6 Feb 2020 16:15:59 +1100 Subject: [Koha-devel] Starting/stopping koha-testing-docker Message-ID: <0d0301d5dcac$849ee870$8ddcb950$@prosentient.com.au> Hi all, Is there a trick for stopping and starting koha-testing-docker, when using docker-compose, so that you can re-use the same containers? I stop/start containers all the time on other projects, and I swear that Tomas told me how to do it with koha-testing-docker, but koha_koha_1 keeps crashing with "User kohadev-koha already exists" after I try to start it after stopping it, as it's trying to run /kohadevbox/run.sh. Perhaps /kohadevbox/run.sh should have a test where it only tries to do setup if it hasn't already setup the container environment. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From jonathan.druart at bugs.koha-community.org Thu Feb 6 10:14:23 2020 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Thu, 6 Feb 2020 10:14:23 +0100 Subject: [Koha-devel] Koha mirror on gitlab.com not updated ? In-Reply-To: <0cd401d5dc96$cc1c27a0$645476e0$@prosentient.com.au> References: <76195246-84f8-cbbd-9c85-f630f30de0f5@biblibre.com> <0cd401d5dc96$cc1c27a0$645476e0$@prosentient.com.au> Message-ID: Next step is: https://wiki.koha-community.org/wiki/Git_Splitting_and_Shrinking I have tried few months ago but almost burnt my CPU, we need a powerful machine to do that. I think some of us plan to work on that during the hackfest in Marseille. No need for me to explain the gitlab.com vs self-hosting, I am sure you know the answers already. Le jeu. 6 févr. 2020 à 03:40, a écrit : > > I’ve been in touch with someone at Gitlab, and they pointed out that https://gitlab.com/gitlab-com/support-forum/issues/4590 is just a forum rather than a bug tracker per se. That said, I see Gitlab employees commenting on other “support-forum” issues like https://gitlab.com/gitlab-com/support-forum/issues/5165. > > > > The information at https://about.gitlab.com/support/#differences-between-support-tickets-and-gitlab-issues is a bit confusing, as it seems to suggest free users can’t open tickets, but https://support.gitlab.com/hc/en-us has an option for free users to open tickets. I was also told that it was fine for free users to open tickets, although there is no SLA governing response times. > > > > I suggest that we submit a new support ticket via https://support.gitlab.com/hc/en-us. If the number is shared with me, I’d be happy to try contacting Gitlab folk via side channels to see if they can prioritize it a bit. > > > > Judging from https://docs.gitlab.com/ee/user/project/repository/reducing_the_repo_size_using_git.html (and some things I’ve heard), it sounds like Gitlab might need to do cleanup work on their end. I don’t think rewriting history is the answer, but maybe they need to do some git garbage collection or do something else to “clean up its own internal state”. > > > > That all being said, while we might solve this problem this once, I imagine it might happen again, so what would our long-term plan be? > > > > Is there a reason we use Gitlab.com instead of self-hosting Gitlab? > > > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > Australia > > > > Office: 02 9212 0899 > > Direct: 02 8005 0595 > > > > From: Koha-devel On Behalf Of Renvoize, Martin > Sent: Thursday, 6 February 2020 5:17 AM > To: Julian Maurice > Cc: koha-devel > Subject: Re: [Koha-devel] Koha mirror on gitlab.com not updated ? > > > > Our repo is certainly a bit on the big side.. but I'm also disappointed in the lack of response from gitlab. > > > > Perhaps we could clarify the issue title a little.. Its not clear from the title that we believe gitlab is estimating the size wrongly > > > > On Wed, 5 Feb 2020, 2:47 pm Julian Maurice, wrote: > > I know there is a mirror on github but the koha-community organization > there has only 4 repositories, including one which points to gitlab.com > (kohadocs), and another that is not directly related to koha (perlweb). > If we compare to gitlab.com where there are 17 repositories, I think we > cannot say that we "moved" to github. > > So, the situation is a little weird as almost all repositories are on > gitlab, except for the main repository which is not updated correctly, > so people have to go elsewhere (github or git.koha-community.org) to get > koha > > Hopefully gitlab will fix the issue. But what if they don't ? :/ > > Le 05/02/2020 à 10:00, Jonathan Druart a écrit : > >> Have you considered moving to github instead ? (github has a hard limit > >> of 100GB per repository) > > > > We moved from github to gitlab a couple of years ago ;) > > > > > >> Le 04/02/2020 à 16:29, Jonathan Druart a écrit : > >>> I investigated that issue few months ago, and asked Chris what > >>> returned `du -sbh .git` on git.koha-community.org/koha: 2.8G .git > >>> So it's really weird that gitlab complains about that size (13GB) > >>> At that time (June 2019) the gitlab interface says "17Go, 7 over the > >>> limit of 10." > >>> So numbers look quite inconsistent. > >>> > >>> See also the issue I opened on their bug tracker: > >>> https://gitlab.com/gitlab-com/support-forum/issues/4590 > >>> > >>> > >>> > >>> Le mar. 4 févr. 2020 à 15:28, Julian Maurice > >>> a écrit : > >>>> > >>>> Can we do something about that or should we consider the mirror on > >>>> gitlab to be useless and never use it ? > >>>> > >>>> Le 04/02/2020 à 14:59, Tomas Cohen Arazi a écrit : > >>>>> Because of Koha's repo size. > >>>>> > >>>>> El mar., 4 feb. 2020 a las 10:55, Julian Maurice > >>>>> (>) > >>>>> escribió: > >>>>> > >>>>> Hi all, > >>>>> > >>>>> It seems the mirror on gitlab is not updated anymore. The last > >>>>> commit on > >>>>> master is > >>>>> > >>>>> 604c7b81 Bug 22816: OPAC detail holdings table should now look a bit > >>>>> better > >>>>> > >>>>> which has been committed in May 2019 > >>>>> > >>>>> Does anyone know why ? > >>>>> > >>>>> -- > >>>>> Julian Maurice > >>>>> BibLibre > >>>>> _______________________________________________ > >>>>> Koha-devel mailing list > >>>>> Koha-devel at lists.koha-community.org > >>>>> > >>>>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > >>>>> website : http://www.koha-community.org/ > >>>>> git : http://git.koha-community.org/ > >>>>> bugs : http://bugs.koha-community.org/ > >>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> Tomás Cohen Arazi > >>>>> Theke Solutions (http://theke.io ) > >>>>> ✆ +54 9351 3513384 > >>>>> GPG: B2F3C15F > >>>> > >>>> -- > >>>> Julian Maurice > >>>> BibLibre > >>>> _______________________________________________ > >>>> Koha-devel mailing list > >>>> Koha-devel at lists.koha-community.org > >>>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > >>>> website : http://www.koha-community.org/ > >>>> git : http://git.koha-community.org/ > >>>> bugs : http://bugs.koha-community.org/ > >> > >> -- > >> Julian Maurice > >> BibLibre > > -- > Julian Maurice > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ From agustinmoyano at theke.io Thu Feb 6 15:12:12 2020 From: agustinmoyano at theke.io (Agustin Moyano) Date: Thu, 6 Feb 2020 11:12:12 -0300 Subject: [Koha-devel] Starting/stopping koha-testing-docker In-Reply-To: <0d0301d5dcac$849ee870$8ddcb950$@prosentient.com.au> References: <0d0301d5dcac$849ee870$8ddcb950$@prosentient.com.au> Message-ID: Hi David, you have 2 ways. First if you started koha-testing-docker using the script alias "ku", the script has the "--force-recreate" flag when it runs.. that means if you kill it, and start it again with ku you wont have any problems. The other way is to not kill the container, but simply do "reset_all" inside docker container... that is basically the same in the way that it will cleanup your database and install everything from scratch. Hope it helps! On Thu, Feb 6, 2020 at 2:16 AM wrote: > Hi all, > > > > Is there a trick for stopping and starting koha-testing-docker, when using > docker-compose, so that you can re-use the same containers? > > > > I stop/start containers all the time on other projects, and I swear that > Tomas told me how to do it with koha-testing-docker, but koha_koha_1 keeps > crashing with “User kohadev-koha already exists” after I try to start it > after stopping it, as it’s trying to run /kohadevbox/run.sh. Perhaps > /kohadevbox/run.sh should have a test where it only tries to do setup if it > hasn’t already setup the container environment. > > > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > Australia > > > > Office: 02 9212 0899 > > Direct: 02 8005 0595 > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Fri Feb 7 00:44:43 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Fri, 7 Feb 2020 10:44:43 +1100 Subject: [Koha-devel] Starting/stopping koha-testing-docker In-Reply-To: References: <0d0301d5dcac$849ee870$8ddcb950$@prosentient.com.au> Message-ID: <0d5401d5dd47$680767f0$381637d0$@prosentient.com.au> Hi Agustin, Thanks for your email. However, I think that perhaps you misunderstand me. I’m not trying to re-create the containers; I’m trying to re-use/re-start the existing containers. Your first suggestion will recreate the containers by destroying the old ones. That means I can’t re-use them. Your second suggestion requires the container to be running, but my use case is starting a stopped container, which has been stopped either manually, by a system reboot, or whatever. I suppose I could modify the docker-compose.yml file to have a custom command, and just manually run /kohadevbox/run.sh when I initially create the container… that might be the shortest path to what I’m trying to do. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Agustin Moyano Sent: Friday, 7 February 2020 1:12 AM To: dcook at prosentient.com.au Cc: koha-devel ; tomascohen at theke.io Subject: Re: [Koha-devel] Starting/stopping koha-testing-docker Hi David, you have 2 ways. First if you started koha-testing-docker using the script alias "ku", the script has the "--force-recreate" flag when it runs.. that means if you kill it, and start it again with ku you wont have any problems. The other way is to not kill the container, but simply do "reset_all" inside docker container... that is basically the same in the way that it will cleanup your database and install everything from scratch. Hope it helps! On Thu, Feb 6, 2020 at 2:16 AM > wrote: Hi all, Is there a trick for stopping and starting koha-testing-docker, when using docker-compose, so that you can re-use the same containers? I stop/start containers all the time on other projects, and I swear that Tomas told me how to do it with koha-testing-docker, but koha_koha_1 keeps crashing with “User kohadev-koha already exists” after I try to start it after stopping it, as it’s trying to run /kohadevbox/run.sh. Perhaps /kohadevbox/run.sh should have a test where it only tries to do setup if it hasn’t already setup the container environment. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From dcook at prosentient.com.au Fri Feb 7 01:18:28 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Fri, 7 Feb 2020 11:18:28 +1100 Subject: [Koha-devel] Starting/stopping koha-testing-docker In-Reply-To: References: <0d0301d5dcac$849ee870$8ddcb950$@prosentient.com.au> <0d5401d5dd47$680767f0$381637d0$@prosentient.com.au> Message-ID: <0d6801d5dd4c$1f2aa880$5d7ff980$@prosentient.com.au> Thanks, Tomas, but the issue isn’t the database. I was probably misleading in my original email. The issue is that the /kohadevbox/run.sh script tries to re-provision the koha_koha_1 server, and it fatally fails to do so. Before doing the setup, it should do a test to see if it needs to do the setup. But the --force-recreate option is practical enough for now. If it bothers me enough going forward, I’ll do a patch and send in a pull request for the run.sh script It’s probably not a bad thing to re-create the containers each time just to have a clean code and configuration environment, but it makes long-term work more difficult. Recently, I created a jboss/keycloak container, and I just start/stop that container whenever I need a Keycloak server. Same with a lot of containers I use. Of course, that means it’s easier for untracked localizations to sneak in and then you destroy the container and create a new one and it’s radically different to what you’re using but *shrug*. Anyway, good to know that we can’t stop/start koha-testing-docker. I thought I was missing something, but it just looks like it’s not possible currently. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Tomas Cohen Arazi Sent: Friday, 7 February 2020 10:55 AM To: David Cook Cc: Agustin Moyano ; koha-devel Subject: Re: [Koha-devel] Starting/stopping koha-testing-docker There's one alias for persistent db. That might suit you El jue., 6 de febrero de 2020 20:45, > escribió: Hi Agustin, Thanks for your email. However, I think that perhaps you misunderstand me. I’m not trying to re-create the containers; I’m trying to re-use/re-start the existing containers. Your first suggestion will recreate the containers by destroying the old ones. That means I can’t re-use them. Your second suggestion requires the container to be running, but my use case is starting a stopped container, which has been stopped either manually, by a system reboot, or whatever. I suppose I could modify the docker-compose.yml file to have a custom command, and just manually run /kohadevbox/run.sh when I initially create the container… that might be the shortest path to what I’m trying to do. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Agustin Moyano > Sent: Friday, 7 February 2020 1:12 AM To: dcook at prosentient.com.au Cc: koha-devel >; tomascohen at theke.io Subject: Re: [Koha-devel] Starting/stopping koha-testing-docker Hi David, you have 2 ways. First if you started koha-testing-docker using the script alias "ku", the script has the "--force-recreate" flag when it runs.. that means if you kill it, and start it again with ku you wont have any problems. The other way is to not kill the container, but simply do "reset_all" inside docker container... that is basically the same in the way that it will cleanup your database and install everything from scratch. Hope it helps! On Thu, Feb 6, 2020 at 2:16 AM > wrote: Hi all, Is there a trick for stopping and starting koha-testing-docker, when using docker-compose, so that you can re-use the same containers? I stop/start containers all the time on other projects, and I swear that Tomas told me how to do it with koha-testing-docker, but koha_koha_1 keeps crashing with “User kohadev-koha already exists” after I try to start it after stopping it, as it’s trying to run /kohadevbox/run.sh. Perhaps /kohadevbox/run.sh should have a test where it only tries to do setup if it hasn’t already setup the container environment. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From marco.wahls at gmx.de Fri Feb 7 21:31:47 2020 From: marco.wahls at gmx.de (M.Wahls) Date: Fri, 7 Feb 2020 21:31:47 +0100 Subject: [Koha-devel] Build the easy way throws error In-Reply-To: References: Message-ID: <4d0dce2a-255a-57fa-8b48-64806e38a30a@gmx.de> Thank you. You helped me a lot! I analysed the docker image and used the description on the webside of the docker image. And was able to get things working using the debian installation on VirtualBox. Here are my steps. There are some litte changes compared to the tutorial in the koha-wiki. May be it helps someone somehow. Debian virtualbox setup min 2GB Ram, 20GB variable Filesystem Downloaded installation media is Debian netinstall (setup includes SSH Server und standard systemtools during package selection). after reboot install the following software: apt-get install devscripts pbuilder dh-make fakeroot debian-archive-keyring libmodern-perl-perl create build image: pbuilder create --distribution stretch pbuilder login --save-after-login export VERSION=19.11 echo "deb http://debian.koha-community.org/koha $VERSION main" > /etc/apt/sources.list.d/koha.list >> To build a package from master, you need the following steps instead of the two mentioned above: >> echo "deb http://debian.koha-community.org/koha unstable main" > /etc/apt/sources.list.d/koha.list >> echo "deb [trusted=yes] http://apt.abunchofthings.net/koha-nightly unstable main" >> /etc/apt/sources.list.d/koha.list >> the rest of the procedure is the same for master and 19.11, >> except checkout after cloning the koha repository. apt install wget gnupg wget -O- http://debian.koha-community.org/koha/gpg.asc | apt-key add - apt update apt install koha-perldeps exit apt-get update apt-get upgrade checkout koha and prepare build: mkdir ~/debian cd ~/debian git clone git://git.koha-community.org/koha.git koha cd koha git checkout -b 19.11.x origin/19.11.x git pull cd .. cp -r koha koha-build mkdir build-result cd koha-build su -c "./debian/build-git-snapshot -r /home/user/debian/build-result -v 19.11.02git -d" cd ../build-result >> check if *.deb-files exist: ls -al Not all steps are importent for the first build, but are usefull later on. best wishes Marco From paul.poulain at biblibre.com Mon Feb 10 15:08:44 2020 From: paul.poulain at biblibre.com (Paul Poulain) Date: Mon, 10 Feb 2020 15:08:44 +0100 Subject: [Koha-devel] hackfest registration Message-ID: Hello koha fans, A quick reminder: drop me an email if you plan to come to the hackfest, that will be in March, 23-27, in France, Marseille. Currently, we've people from : Argentina, Canada, Finland, France, Germany, Ireland, Spain, UK, USA. Your country and your contribution is missing !!! As usual, it will be a week of useful work, with a lot of documenting, testing, coding, talking, thinking. And a little bit of eating (cheese) and drinking ( -not only- beer, after work of course) Welcome -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries From martin.renvoize at ptfs-europe.com Tue Feb 11 10:54:23 2020 From: martin.renvoize at ptfs-europe.com (Renvoize, Martin) Date: Tue, 11 Feb 2020 09:54:23 +0000 Subject: [Koha-devel] Coding guidelines In-Reply-To: References: Message-ID: Ooops, I forgot to reply to this. It looks good to me Marcel. *Martin Renvoize* Development Team Manager Community Release Manager (19.11, 20.05) *Phone:* +44 (0) 1483 378728 *Mobile:* +44 (0) 7725 985 636 *Email:* martin.renvoize at ptfs-europe.com *Fax:* +44 (0) 800 756 6384 www.ptfs-europe.com Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info at ptfs-europe.com On Wed, 29 Jan 2020 at 16:25, Marcel de Rooy wrote: > Referring to the dev meeting and bug 22407, I propose the following > rewording: > > PERL15 Using Koha::Object[s] > PERL15(a) Code added to the Koha:: namespace should be object-oriented > unless there is a very good reason to do otherwise. In that case the reason > should be documented clearly. > PERL15(b) Code in Koha::Object[s] should normally not refer back to C4. > Obviously, this cannot be enforced harshly until the refactoring has been > completed. > PERL15(c) Use DBIC relations to (pre)fetch a related Koha object rather > than searching it explicitly. (See bug 22407) > > > PERL28 Other object oriented code guidelines (in addition to PERL15) > I think we need to move the Accessor and idiom for -> new rules from > PERL15 to another rule. I opened rule 28 for that depending on discussing > the following: > Class::Accessor is a great way to provide access to member variables. > => My suggestion would be to remove this rule. It is true but we do not > say that it is the only way to do it. (We are not even using > Class::Accessor in Koha objects.) > Or just say PERL28(a) To provide access to member variables, there are > several ways including but not limited to using Class::Accessor. > > A useful idiom for the ->new() routine in object-oriented classes that do > not need to process the arguments passed in as a hashref but merely need to > save them for future processing > => This suggestion is fine. It says use a parameter hash for sub new. We > normally do that. Reworded: > PERL 28(b) Use a hashref as second parameter in sub new when passing > arguments. > > Any feedback? > > Marcel > ​ > [image: http://www.rijksmuseum.nl] > > ​Museumstraat 1 > Postbus 74888 > 1070 DN Amsterdam > *Rijksmuseum.nl* > ​ > ​Nu te zien: > *Operatie Nachtwacht​* > ​ > ​Verwacht: > ​*Caravaggio-Bernini. Barok in Rome* > > *​Dankzij Waller 2010-2020* > > > ​ > ​T/m 18 jaar gratis > > Please think before you print > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image826795.png Type: image/png Size: 2974 bytes Desc: not available URL: From jonathan.druart at bugs.koha-community.org Tue Feb 11 11:41:12 2020 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Tue, 11 Feb 2020 11:41:12 +0100 Subject: [Koha-devel] Starting/stopping koha-testing-docker In-Reply-To: <0d0301d5dcac$849ee870$8ddcb950$@prosentient.com.au> References: <0d0301d5dcac$849ee870$8ddcb950$@prosentient.com.au> Message-ID: David, I think what you want is do_all_you_can_do.pl (from koha-misc4dev) to stop if populate_db.pl die with "DB not empty" Cheers, Jonathan Le jeu. 6 févr. 2020 à 06:15, a écrit : > > Hi all, > > > > Is there a trick for stopping and starting koha-testing-docker, when using docker-compose, so that you can re-use the same containers? > > > > I stop/start containers all the time on other projects, and I swear that Tomas told me how to do it with koha-testing-docker, but koha_koha_1 keeps crashing with “User kohadev-koha already exists” after I try to start it after stopping it, as it’s trying to run /kohadevbox/run.sh. Perhaps /kohadevbox/run.sh should have a test where it only tries to do setup if it hasn’t already setup the container environment. > > > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > Australia > > > > Office: 02 9212 0899 > > Direct: 02 8005 0595 > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ From martin.renvoize at ptfs-europe.com Thu Feb 13 10:39:40 2020 From: martin.renvoize at ptfs-europe.com (Renvoize, Martin) Date: Thu, 13 Feb 2020 09:39:40 +0000 Subject: [Koha-devel] GBSD - Global Bug Squashing Day Tomorrow Message-ID: Hi All, Just a little reminder we have a global bug squashing day scheduled for tomorrow. I look forward to seeing lots of you on IRC and in the bug mails.. Have a great day :) *Martin Renvoize* Development Team Manager Community Release Manager (19.11, 20.05) *Phone:* +44 (0) 1483 378728 *Mobile:* +44 (0) 7725 985 636 *Email:* martin.renvoize at ptfs-europe.com *Fax:* +44 (0) 800 756 6384 www.ptfs-europe.com Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info at ptfs-europe.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From hagud at orex.es Thu Feb 13 13:22:29 2020 From: hagud at orex.es (Hugo Agud) Date: Thu, 13 Feb 2020 13:22:29 +0100 Subject: [Koha-devel] issue with kohadevbox Message-ID: Good morning I am trying to be ready for tomorrow, I have installed a new kohadev box and in weinstaller I am getting this error Can't locate object method "phases" via package "CPAN::Meta::Prereqs" at /home/vagrant/kohaclone/C4/Installer/PerlModules.pm line 55 - in C4::Installer::PerlModules::versions_info at /home/vagrant/kohaclone/C4/Installer/PerlModules.pm line 55 52: $self->{'upgrade_pm'} = []; 53: $self->{'current_pm'} = []; 54: * 55: foreach my $phase ($self->prereqs->phases) { * 56: foreach my $type ($self->prereqs->types_in($phase)) { 57: my $reqs = $self->prereqs->requirements_for($phase, $type); 58: foreach my $module ($reqs->required_modules) { Show function arguments - in (eval) at /home/vagrant/kohaclone/installer/install.pl line 102 99: } 100: 101: my $perl_modules = C4::Installer::PerlModules->new;* 102: $perl_modules->versions_info; * 103: 104: my $missing_modules = $perl_modules->get_attr('missing_pm'); 105: my $upgrade_modules = $perl_modules->get_attr('upgrade_pm'); I am going to skip web installer -- *Hugo Agud - Orex Digital * *www.orex.es * [image: www.orex.es/koha] [image: www.orex.es/vufind] Director Passeig Comte Vilardaga, 118 3-3 08980 -Sant Feliu de Llobregat - Tel: 933 856 138 hagud at orex.es · http://www.orex.es/ No imprima este mensaje a no ser que sea necesario. Una tonelada de papel implica la tala de 15 árboles y el consumo de 250.000 litros de agua. Aviso de confidencialidad Este mensaje contiene información que puede ser CONFIDENCIAL y/o de USO RESTRINGIDO. Si usted no es el receptor deseado del mensaje (ni está autorizado a recibirlo por el remitente), no está autorizado a copiar, reenviar o divulgar el mensaje o su contenido. Si ha recibido este mensaje por error, por favor, notifíquenoslo inmediatamente y bórrelo de su sistema. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Thu Feb 13 13:30:03 2020 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Thu, 13 Feb 2020 13:30:03 +0100 Subject: [Koha-devel] issue with kohadevbox In-Reply-To: References: Message-ID: Hi Hugo, Install/update the package: sudo apt install libcpan-meta-perl See also bug 19735 (last comments). Cheers, Jonathan Le jeu. 13 févr. 2020 à 13:22, Hugo Agud a écrit : > Good morning > > I am trying to be ready for tomorrow, I have installed a new kohadev box > and in weinstaller I am getting this error > > Can't locate object method "phases" via package "CPAN::Meta::Prereqs" at /home/vagrant/kohaclone/C4/Installer/PerlModules.pm line 55 > > > - in C4::Installer::PerlModules::versions_info at > /home/vagrant/kohaclone/C4/Installer/PerlModules.pm line 55 > > 52: $self->{'upgrade_pm'} = []; > 53: $self->{'current_pm'} = []; > 54: * 55: foreach my $phase ($self->prereqs->phases) { > * 56: foreach my $type ($self->prereqs->types_in($phase)) { > 57: my $reqs = $self->prereqs->requirements_for($phase, $type); > 58: foreach my $module ($reqs->required_modules) { > > Show function arguments > - in (eval) at /home/vagrant/kohaclone/installer/install.pl line 102 > > 99: } > 100: > 101: my $perl_modules = C4::Installer::PerlModules->new;* 102: $perl_modules->versions_info; > * 103: > 104: my $missing_modules = $perl_modules->get_attr('missing_pm'); > 105: my $upgrade_modules = $perl_modules->get_attr('upgrade_pm'); > > > I am going to skip web installer > > -- > > *Hugo Agud - Orex Digital * > > *www.orex.es * > > > [image: www.orex.es/koha] > [image: www.orex.es/vufind] > > > > Director > > Passeig Comte Vilardaga, 118 3-3 08980 -Sant Feliu de Llobregat - Tel: > 933 856 138 hagud at orex.es · http://www.orex.es/ > > > > No imprima este mensaje a no ser que sea necesario. Una tonelada de papel > implica la tala de 15 árboles y el consumo de 250.000 litros de agua. > > > > Aviso de confidencialidad > Este mensaje contiene información que puede ser CONFIDENCIAL y/o de USO > RESTRINGIDO. Si usted no es el receptor deseado del mensaje (ni > está autorizado a recibirlo por el remitente), no está autorizado a > copiar, reenviar o divulgar el mensaje o su contenido. Si ha recibido este > mensaje > por error, por favor, notifíquenoslo inmediatamente y bórrelo de su > sistema. > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kohanews at gmail.com Fri Feb 14 02:10:19 2020 From: kohanews at gmail.com (kohanews) Date: Thu, 13 Feb 2020 17:10:19 -0800 Subject: [Koha-devel] Call for news: February 2020 Koha Newsletter Message-ID: <5043b1c6-80b2-4988-f4be-5b66071402eb@gmail.com> I'm collecting news for the February 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 From joy at bywatersolutions.com Fri Feb 14 18:27:41 2020 From: joy at bywatersolutions.com (Joy Nelson) Date: Fri, 14 Feb 2020 10:27:41 -0700 Subject: [Koha-devel] String Freeze Notice Message-ID: Greetings! Just a quick note that string freeze will go into effect on 2/15/2020 for the maintenance branches. Maintenance releases scheduled for the 22rd. Happy Valentines Day! -- Joy Nelson President, Koha Division ByWater Solutions Support and Consulting for Open Source Software Phone/Fax (888)900-8944 What is Koha? -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Mon Feb 17 02:00:06 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Mon, 17 Feb 2020 12:00:06 +1100 Subject: [Koha-devel] Adding peer review status to article records Message-ID: <014c01d5e52d$981cf020$c856d060$@prosentient.com.au> Hi all, I have a library interested in adding peer review status to their article records in Koha. The short-term solution is to use a local MARC field and do a code customization for it. However, peer review status is the kind of thing that the library industry will probably see more and more of going forward into the digital future. It seems to me that a long-term solution would be wiser. Sure enough, ExLibris Alma and OCLC WorldCat Discovery already have this functionality: https://help.oclc.org/Discovery_and_Reference/WorldCat_Discovery/Search_resu lts/How_item_bibliographic_data_is_displayed https://knowledge.exlibrisgroup.com/Alma/Release_Notes/010_2018/11_February_ 2018/Alma_February_2018_Release_Notes/02Resource_Management_-_February_2018_ Enhancements#Peer_Review_and_Open_Access OCLC uses a non-MARC method, whereas ExLibris rely on a magic string in a 500 field for peer review status. That being said, I'm not sure what the best long-term solution would be to add this metadata to a bibliographic record. What do you all think? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From dcook at prosentient.com.au Mon Feb 17 02:05:21 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Mon, 17 Feb 2020 12:05:21 +1100 Subject: [Koha-devel] Adding peer review status to article records In-Reply-To: <014c01d5e52d$981cf020$c856d060$@prosentient.com.au> References: <014c01d5e52d$981cf020$c856d060$@prosentient.com.au> Message-ID: <015b01d5e52e$53c6a000$fb53e000$@prosentient.com.au> It does have me thinking. we already have the biblio_metadata table set up to allow arbitrary metadata to be added to a bibliographic record. Really we just need a system for doing CRUD, have code for rendering views of the data, and code for allowing that data to be searchable*. In terms of CRUD, data rendering, and I suppose even indexing, plugins might be a useful way to experiment with this functionality. (Of course, there's always the danger that people go off on a million different custom pathways which makes support a nightmare.) This also has me thinking about RDF/Linked Data. I think in the past I had too much of an hopelessly idealist vision of how Linked Data should work, but Fedora Commons has inspired me to see RDF as just another metadata format that can handle countless schemas. With Fedora Commons, the subject URI is your web URI, the predicate is whatever schema URI you want to use, and then the object is often a literal string. Fedora Commons doesn't use a triplestore out of the box, so we don't need to worry about that right now. We could just store some RDF/XML or JSON-LD in the biblio_metadata table (personally I like working programmatically with JSON-LD but RDF/XML is probably more MySQL friendly due to its XML parsing functionality - although MariaDB 10.2 adds JSON support I think which should be available in Debian Buster. RDF/XML would also be XSLT friendly). *Technically, Zebra can handle any XML, but we just give it MARCXML. There's no reason Zebra couldn't handle more XML-based formats. That being said, I think we've all agreed Elasticsearch is the future, and I think there's already work done/being done on that to allow arbitrary metadata to be added? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Koha-devel On Behalf Of dcook at prosentient.com.au Sent: Monday, 17 February 2020 12:00 PM To: 'koha-devel' Subject: [Koha-devel] Adding peer review status to article records Hi all, I have a library interested in adding peer review status to their article records in Koha. The short-term solution is to use a local MARC field and do a code customization for it. However, peer review status is the kind of thing that the library industry will probably see more and more of going forward into the digital future. It seems to me that a long-term solution would be wiser. Sure enough, ExLibris Alma and OCLC WorldCat Discovery already have this functionality: https://help.oclc.org/Discovery_and_Reference/WorldCat_Discovery/Search_resu lts/How_item_bibliographic_data_is_displayed https://knowledge.exlibrisgroup.com/Alma/Release_Notes/010_2018/11_February_ 2018/Alma_February_2018_Release_Notes/02Resource_Management_-_February_2018_ Enhancements#Peer_Review_and_Open_Access OCLC uses a non-MARC method, whereas ExLibris rely on a magic string in a 500 field for peer review status. That being said, I'm not sure what the best long-term solution would be to add this metadata to a bibliographic record. What do you all think? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From dcook at prosentient.com.au Mon Feb 17 02:45:20 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Mon, 17 Feb 2020 12:45:20 +1100 Subject: [Koha-devel] Alternative views for search results and detail pages? Message-ID: <016901d5e533$e9927500$bcb75f00$@prosentient.com.au> Hi all, What do people think about replacing the XSLTs with Template Toolkit templates for search results and detail pages? Considering that the OPAC Detail XSLT is 2000 lines and the Search Result XSLT is 1500 lines (and that doesn't include the utility XSLT) maybe that's a bit ambitious. The Intranet Search results are 1000 lines and Intranet Detail is 1600 lines. I'm just trying to think of how we could do views for metadata that aren't MARC-centric. Actually, after reviewing the XSLTs, I suppose there's no reason we couldn't expand the XSLTs to include more metadata schema options. We could actually provide any XML and then just do an XSLT template to render it. (After looking at Koha::SearchEngine::Elasticsearch::Search, it looks like we're storing whole MARCXML records in Elasticsearch, and that's what we're fetching from Elasticsearch for Koha to render for views?) Looking at biblio-zebra-indexdefs.xsl and really we could hand that arbitrary XML to index as well. and then worry about C4::Search::getRecords() stuffing the Zebra raw record into the result data structure and C4::Search::searchResults assuming it's a MARCXML record. It's too bad MARC::Record::XML doesn't check for a XML::LibXML object before trying to parse, or we could parse the XML and then just hand the relevant XML to MARC::Record. I mean we could still do that but it would involve double-parsing, which would be a performance hit. Although I imagine Galen wouldn't necessarily be opposed to accepting an update. I mean it would basically be adding the same functionality to Zebra that we have with Elasticsearch, no? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From jonathan.druart at bugs.koha-community.org Mon Feb 17 11:57:19 2020 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Mon, 17 Feb 2020 11:57:19 +0100 Subject: [Koha-devel] Coding guidelines In-Reply-To: References: Message-ID: Hi Marcel, Sorry for the late reply. All looks ok to me as well, only a couple of things: 15b: better to point to C4 than c/p code from there to Koha :) Ideally the code should be moved to Koha, then used from there. But no always a solution I guess. 15c: On 22407 comment 3 I listed the different cases of the relationship, and how we should use them. ie. no "return unless" if not necessary, etc. I think they could be copied to the wiki as an example to follow https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22407#c3 And a question about 15a, what could be a good reason to not use OOP in Koha? Thanks! Jonathan Le mer. 29 janv. 2020 à 17:24, Marcel de Rooy a écrit : > Referring to the dev meeting and bug 22407, I propose the following > rewording: > > PERL15 Using Koha::Object[s] > PERL15(a) Code added to the Koha:: namespace should be object-oriented > unless there is a very good reason to do otherwise. In that case the reason > should be documented clearly. > PERL15(b) Code in Koha::Object[s] should normally not refer back to C4. > Obviously, this cannot be enforced harshly until the refactoring has been > completed. > PERL15(c) Use DBIC relations to (pre)fetch a related Koha object rather > than searching it explicitly. (See bug 22407) > > > PERL28 Other object oriented code guidelines (in addition to PERL15) > I think we need to move the Accessor and idiom for -> new rules from > PERL15 to another rule. I opened rule 28 for that depending on discussing > the following: > Class::Accessor is a great way to provide access to member variables. > => My suggestion would be to remove this rule. It is true but we do not > say that it is the only way to do it. (We are not even using > Class::Accessor in Koha objects.) > Or just say PERL28(a) To provide access to member variables, there are > several ways including but not limited to using Class::Accessor. > > A useful idiom for the ->new() routine in object-oriented classes that do > not need to process the arguments passed in as a hashref but merely need to > save them for future processing > => This suggestion is fine. It says use a parameter hash for sub new. We > normally do that. Reworded: > PERL 28(b) Use a hashref as second parameter in sub new when passing > arguments. > > Any feedback? > > Marcel > ​ > [image: http://www.rijksmuseum.nl] > > ​Museumstraat 1 > Postbus 74888 > 1070 DN Amsterdam > *Rijksmuseum.nl* > ​ > ​Nu te zien: > *Operatie Nachtwacht​* > ​ > ​Verwacht: > ​*Caravaggio-Bernini. Barok in Rome* > > *​Dankzij Waller 2010-2020* > > > ​ > ​T/m 18 jaar gratis > > Please think before you print > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image826795.png Type: image/png Size: 2974 bytes Desc: not available URL: From saklayan18 at gmail.com Mon Feb 17 12:34:52 2020 From: saklayan18 at gmail.com (Sarowar Saklayan) Date: Mon, 17 Feb 2020 17:34:52 +0600 Subject: [Koha-devel] About SMS integration with KOHA 19.11 from Bangladesh. Message-ID: Dear Sir, We are here trying to integrate SMS API with KOHA but failed. If there any suggestions for us or any alternative option. Please let us know. -- Regards Md. Sarowar Saklayan CRO & System Analyst Dhaka | Rajshahi | Chattogram | Kolkata | Pennsylvania Cell phone:+8801913800800, +8801729018635 Fax: +880 721 774373, E-mail: saklayan18 at gmail.com Web: DesktopIT.com.bd | WebRajshahi.com | KhazaCorporation.com IM - "01729018635" (Skype & whatsApp) -------------- next part -------------- An HTML attachment was scrubbed... URL: From julian.maurice at biblibre.com Mon Feb 17 18:59:06 2020 From: julian.maurice at biblibre.com (Julian Maurice) Date: Mon, 17 Feb 2020 18:59:06 +0100 Subject: [Koha-devel] Minimal docker images for Koha Message-ID: Hi all, I've been playing with docker lately, and I tried to build a minimal docker image for Koha. Here are the results. My goals were: * Install only required "things" to get Koha up and running, and nothing else (no testing or dev tools), * No external dependencies except CPAN * Follow Docker best practices as much as possible The resulting images are here: https://hub.docker.com/repository/docker/julianmaurice/koha and the Dockerfiles are here: https://github.com/jajm/koha-docker A few things worth mentioning: * I tried to build the smallest image possible by using alpine or perl slim images at first but it was not that great, because the perl version shipped with those images is missing some libs, which cause MARC::Charset to build a database of several hundreds MBs (which is only 5MBs with a standard perl version). So I chose a more standard image (debian:buster) as base. * Koha doesn't work well when running with a perl version different than the system perl installed in /usr/bin/perl. For example, the updatedatabase doesn't work when called from the web installer. This is because Perl scripts are called directly as executable files, and shebangs contain '/usr/bin/perl'. Same problem from misc/translator/translate which calls tmpl_process3.pl. * I tried to make the Koha installation as self-contained as possible. Almost everything is installed as a non-root user in /home/koha, including Perl dependencies. * It doesn't need a reverse proxy such as apache or nginx. The necessary URL rewriting is handled in PSGI file. The container expose two ports, one for intranet, the other one for OPAC. * Each Perl dependency is installed in its latest version, so expect things to break. I can only confirm that the webinstaller, basic cataloguing and search/indexation work. I did not test anything else. * There are docker-compose.yml files in the github repository to get Koha running quickly with mariadb, memcached and elasticsearch. * Zebra is not installed * Images weigh ~1.15GB uncompressed (koha sources included) If you made it this far, thanks for reading :) And if you want to use these docker images, you should start by reading https://github.com/jajm/koha-docker/blob/master/README.md -- Julian Maurice BibLibre From dcook at prosentient.com.au Tue Feb 18 00:22:38 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Tue, 18 Feb 2020 10:22:38 +1100 Subject: [Koha-devel] About SMS integration with KOHA 19.11 from Bangladesh. In-Reply-To: References: Message-ID: <021101d5e5e9$251ce910$6f56bb30$@prosentient.com.au> Could you be more specific about what SMS Gateway you’re trying to use and how you’re trying to use it? You could take a look at https://metacpan.org/pod/SMS::Send::UK::Kapow and model your own SMS driver on that (which itself is just building off of SMS::Send::Driver https://metacpan.org/pod/SMS::Send::Driver). The main method you’ll need to customize for your SMS Gateway API is “send_sms”. Here in Australia, we’ve written a couple drivers for some Australian SMS Gateways. I create tarballs of the driver code (which include a Build.PL file) and then I use “cpanm” to install them. (Alternatively, you could build OS packages from them as well, which would be a more scalable approach.) Once the drivers are installed in the system, then you can reference them using the “SMSSendDriver” system preference in Koha. You can also use the “sms_send_config” configuration option in koha-conf.xml to set Koha instance specific SMS driver configuration. If you share some more details, I’m sure we can help you out more. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Koha-devel On Behalf Of Sarowar Saklayan Sent: Monday, 17 February 2020 10:35 PM To: Koha-devel at lists.koha-community.org Subject: [Koha-devel] About SMS integration with KOHA 19.11 from Bangladesh. Dear Sir, We are here trying to integrate SMS API with KOHA but failed. If there any suggestions for us or any alternative option. Please let us know. -- Regards Md. Sarowar Saklayan CRO & System Analyst Dhaka | Rajshahi | Chattogram | Kolkata | Pennsylvania Cell phone:+8801913800800, +8801729018635 Fax: +880 721 774373, E-mail: saklayan18 at gmail.com Web: DesktopIT.com.bd | WebRajshahi.com | KhazaCorporation.com IM - "01729018635" (Skype & whatsApp) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From dcook at prosentient.com.au Tue Feb 18 01:25:10 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Tue, 18 Feb 2020 11:25:10 +1100 Subject: [Koha-devel] Minimal docker images for Koha In-Reply-To: References: Message-ID: <021f01d5e5f1$e16be000$a443a000$@prosentient.com.au> Hi Julian, Awesome to see you playing with Docker. I love Docker and I've been thinking about assembling similar Docker images for Koha, but haven't had the time, so hurray for you doing it! I couldn't get your first URL to work as I think that's an authorised user link. Is it safe to say that this is the public link? https://hub.docker.com/r/julianmaurice/koha Did you try the "debian:buster-slim" image? I keep meaning to look to see what makes these Koha images so large. With an interpreted language like Perl and Koha's immense functionality, I think it would be challenging to get a small image size. RedHat's registry.access.redhat.com/ubi8/perl-526 image is 658MB and that's without anything application specific even installed. That being said, I think I see some places where you could improve your Dockerfile. Have you checked out multi-stage builds at https://docs.docker.com/develop/develop-images/multistage-build/? In your final image, you shouldn't need packages like gcc, git, *-dev, make, cpanm, etc. You can install those in a "builder" image and do the Koha build there. Then you can copy your Perl libraries and built Koha into the final image. That should also help you cut down on the number of layers you have. Nice work identifying those system perl dependencies. I keep thinking how we should minimize those. It should be reasonably easy to fix those. Actually, if Koha and its Perl dependencies are localized, you could override those with a mounted volume... which makes me wonder why you couldn't use a more minimal Linux... I've actually been meaning to make some OpenSUSE Koha images which would help test out the concept of a minimal Koha running on something other than Debian as well, although one may as well use Debian, since that's the supported OS for Koha... David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -----Original Message----- From: Koha-devel On Behalf Of Julian Maurice Sent: Tuesday, 18 February 2020 4:59 AM To: koha-devel Subject: [Koha-devel] Minimal docker images for Koha Hi all, I've been playing with docker lately, and I tried to build a minimal docker image for Koha. Here are the results. My goals were: * Install only required "things" to get Koha up and running, and nothing else (no testing or dev tools), * No external dependencies except CPAN * Follow Docker best practices as much as possible The resulting images are here: https://hub.docker.com/repository/docker/julianmaurice/koha and the Dockerfiles are here: https://github.com/jajm/koha-docker A few things worth mentioning: * I tried to build the smallest image possible by using alpine or perl slim images at first but it was not that great, because the perl version shipped with those images is missing some libs, which cause MARC::Charset to build a database of several hundreds MBs (which is only 5MBs with a standard perl version). So I chose a more standard image (debian:buster) as base. * Koha doesn't work well when running with a perl version different than the system perl installed in /usr/bin/perl. For example, the updatedatabase doesn't work when called from the web installer. This is because Perl scripts are called directly as executable files, and shebangs contain '/usr/bin/perl'. Same problem from misc/translator/translate which calls tmpl_process3.pl. * I tried to make the Koha installation as self-contained as possible. Almost everything is installed as a non-root user in /home/koha, including Perl dependencies. * It doesn't need a reverse proxy such as apache or nginx. The necessary URL rewriting is handled in PSGI file. The container expose two ports, one for intranet, the other one for OPAC. * Each Perl dependency is installed in its latest version, so expect things to break. I can only confirm that the webinstaller, basic cataloguing and search/indexation work. I did not test anything else. * There are docker-compose.yml files in the github repository to get Koha running quickly with mariadb, memcached and elasticsearch. * Zebra is not installed * Images weigh ~1.15GB uncompressed (koha sources included) If you made it this far, thanks for reading :) And if you want to use these docker images, you should start by reading https://github.com/jajm/koha-docker/blob/master/README.md -- Julian Maurice BibLibre _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From julian.maurice at biblibre.com Tue Feb 18 07:09:27 2020 From: julian.maurice at biblibre.com (Julian Maurice) Date: Tue, 18 Feb 2020 07:09:27 +0100 Subject: [Koha-devel] Minimal docker images for Koha In-Reply-To: <021f01d5e5f1$e16be000$a443a000$@prosentient.com.au> References: <021f01d5e5f1$e16be000$a443a000$@prosentient.com.au> Message-ID: <6b76f520-ead4-e215-4c74-e2c90f717e39@biblibre.com> The correct URL is indeed https://hub.docker.com/r/julianmaurice/koha Sorry for that :) I just tried buster-slim. The resulting image is 1.06GB. That's ~100MB less than with buster, not bad. But the debian page on dockerhub also states that "These tags are an experiment [...] and are definitely subject to change" so I prefer to stay on the non-slim variant for now. I also tried multi-stage builds, but I didn't like the fact that it leaves an untagged image after each build. Also I figured we might need the build tools once in the container, to install a missing Perl module for instance. And to be honest, after the "failures" of alpine and perl-slim, I decided it was not worth it to try to build the smallest image possible. But you're right, using multi-stage builds we can further reduce the final image size. And if you really really want the smallest image, I think you should use alpine and recompile perl with the correct flags to avoid the MARC::Charset problem. I estimated that you could have an image of 800MB or less. About mounted volumes, from what I understand volumes are for mutable data, and it's considered bad practice to use them for anything else. I would really like to see a non-Debian based image of Koha. It should be relatively easy to do so, by replacing the apt-get command with the corresponding one for OpenSUSE. Le 18/02/2020 à 01:25, dcook at prosentient.com.au a écrit : > Hi Julian, > > Awesome to see you playing with Docker. I love Docker and I've been thinking about assembling similar Docker images for Koha, but haven't had the time, so hurray for you doing it! > > I couldn't get your first URL to work as I think that's an authorised user link. Is it safe to say that this is the public link? https://hub.docker.com/r/julianmaurice/koha > > Did you try the "debian:buster-slim" image? I keep meaning to look to see what makes these Koha images so large. With an interpreted language like Perl and Koha's immense functionality, I think it would be challenging to get a small image size. RedHat's registry.access.redhat.com/ubi8/perl-526 image is 658MB and that's without anything application specific even installed. > > That being said, I think I see some places where you could improve your Dockerfile. Have you checked out multi-stage builds at https://docs.docker.com/develop/develop-images/multistage-build/? In your final image, you shouldn't need packages like gcc, git, *-dev, make, cpanm, etc. You can install those in a "builder" image and do the Koha build there. Then you can copy your Perl libraries and built Koha into the final image. That should also help you cut down on the number of layers you have. > > Nice work identifying those system perl dependencies. I keep thinking how we should minimize those. It should be reasonably easy to fix those. > > Actually, if Koha and its Perl dependencies are localized, you could override those with a mounted volume... which makes me wonder why you couldn't use a more minimal Linux... > > I've actually been meaning to make some OpenSUSE Koha images which would help test out the concept of a minimal Koha running on something other than Debian as well, although one may as well use Debian, since that's the supported OS for Koha... > > David Cook > Systems Librarian > Prosentient Systems > 72/330 Wattle St > Ultimo, NSW 2007 > Australia > > Office: 02 9212 0899 > Direct: 02 8005 0595 > > -----Original Message----- > From: Koha-devel On Behalf Of Julian Maurice > Sent: Tuesday, 18 February 2020 4:59 AM > To: koha-devel > Subject: [Koha-devel] Minimal docker images for Koha > > Hi all, > > I've been playing with docker lately, and I tried to build a minimal docker image for Koha. Here are the results. > > My goals were: > * Install only required "things" to get Koha up and running, and nothing else (no testing or dev tools), > * No external dependencies except CPAN > * Follow Docker best practices as much as possible > > The resulting images are here: > https://hub.docker.com/repository/docker/julianmaurice/koha > > and the Dockerfiles are here: > https://github.com/jajm/koha-docker > > A few things worth mentioning: > > * I tried to build the smallest image possible by using alpine or perl slim images at first but it was not that great, because the perl version shipped with those images is missing some libs, which cause MARC::Charset to build a database of several hundreds MBs (which is only 5MBs with a standard perl version). So I chose a more standard image > (debian:buster) as base. > > * Koha doesn't work well when running with a perl version different than the system perl installed in /usr/bin/perl. For example, the updatedatabase doesn't work when called from the web installer. This is because Perl scripts are called directly as executable files, and shebangs contain '/usr/bin/perl'. Same problem from misc/translator/translate which calls tmpl_process3.pl. > > * I tried to make the Koha installation as self-contained as possible. > Almost everything is installed as a non-root user in /home/koha, including Perl dependencies. > > * It doesn't need a reverse proxy such as apache or nginx. The necessary URL rewriting is handled in PSGI file. The container expose two ports, one for intranet, the other one for OPAC. > > * Each Perl dependency is installed in its latest version, so expect things to break. I can only confirm that the webinstaller, basic cataloguing and search/indexation work. I did not test anything else. > > * There are docker-compose.yml files in the github repository to get Koha running quickly with mariadb, memcached and elasticsearch. > > * Zebra is not installed > > * Images weigh ~1.15GB uncompressed (koha sources included) > > If you made it this far, thanks for reading :) And if you want to use these docker images, you should start by reading https://github.com/jajm/koha-docker/blob/master/README.md > > -- > Julian Maurice > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ > -- Julian Maurice BibLibre From dcook at prosentient.com.au Tue Feb 18 07:29:42 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Tue, 18 Feb 2020 17:29:42 +1100 Subject: [Koha-devel] Minimal docker images for Koha In-Reply-To: <6b76f520-ead4-e215-4c74-e2c90f717e39@biblibre.com> References: <021f01d5e5f1$e16be000$a443a000$@prosentient.com.au> <6b76f520-ead4-e215-4c74-e2c90f717e39@biblibre.com> Message-ID: <027401d5e624$ce159630$6a40c290$@prosentient.com.au> That sounds reasonable regarding buster-slim. I was thinking a minimal Koha in terms of something that would never really be entered, but rather re-generated if there were any problems. But I agree about it not being worth trying to get the smallest image possible. I think that's small image size is overly fetishized. (That said, I love my "from scratch" images that only have a single binary in them, which are absolutely tiny hehe.) That's a good point about the volumes. I suppose I was thinking about it from a testing perspective, but that defeats the purpose. I was actually wondering earlier how many packaged dependencies Koha really has. Off the top of my head, I think the main ones are Apache httpd, Zebra/YAZ, and Mysql client libraries. It looks like "unzip" is needed as well. A number of the other dependencies like xmlstarlet, tinymce, libjs-jquery, mysql, etc are just for the Debian packages. (Actually, I think there is a mysql client binary use in one of the unit tests which seems suboptimal.) Oh, and due to your use of that static file middleware, Apache httpd isn't even needed. A person could probably run the Zebra server in a different container, share a mounted volume for the data, and then just have Zebra/yaz client software in the Koha container. Or if you went the Elasticsearch route, you wouldn't need Zebra at all, right? So in theory you could maybe get away just with "unzip" as a dependency that needs installing via a package manager? (Technically, we could use pure Perl unzip modules as well...) David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -----Original Message----- From: Julian Maurice Sent: Tuesday, 18 February 2020 5:09 PM To: dcook at prosentient.com.au; 'koha-devel' Subject: Re: [Koha-devel] Minimal docker images for Koha The correct URL is indeed https://hub.docker.com/r/julianmaurice/koha Sorry for that :) I just tried buster-slim. The resulting image is 1.06GB. That's ~100MB less than with buster, not bad. But the debian page on dockerhub also states that "These tags are an experiment [...] and are definitely subject to change" so I prefer to stay on the non-slim variant for now. I also tried multi-stage builds, but I didn't like the fact that it leaves an untagged image after each build. Also I figured we might need the build tools once in the container, to install a missing Perl module for instance. And to be honest, after the "failures" of alpine and perl-slim, I decided it was not worth it to try to build the smallest image possible. But you're right, using multi-stage builds we can further reduce the final image size. And if you really really want the smallest image, I think you should use alpine and recompile perl with the correct flags to avoid the MARC::Charset problem. I estimated that you could have an image of 800MB or less. About mounted volumes, from what I understand volumes are for mutable data, and it's considered bad practice to use them for anything else. I would really like to see a non-Debian based image of Koha. It should be relatively easy to do so, by replacing the apt-get command with the corresponding one for OpenSUSE. Le 18/02/2020 à 01:25, dcook at prosentient.com.au a écrit : > Hi Julian, > > Awesome to see you playing with Docker. I love Docker and I've been thinking about assembling similar Docker images for Koha, but haven't had the time, so hurray for you doing it! > > I couldn't get your first URL to work as I think that's an authorised > user link. Is it safe to say that this is the public link? > https://hub.docker.com/r/julianmaurice/koha > > Did you try the "debian:buster-slim" image? I keep meaning to look to see what makes these Koha images so large. With an interpreted language like Perl and Koha's immense functionality, I think it would be challenging to get a small image size. RedHat's registry.access.redhat.com/ubi8/perl-526 image is 658MB and that's without anything application specific even installed. > > That being said, I think I see some places where you could improve your Dockerfile. Have you checked out multi-stage builds at https://docs.docker.com/develop/develop-images/multistage-build/? In your final image, you shouldn't need packages like gcc, git, *-dev, make, cpanm, etc. You can install those in a "builder" image and do the Koha build there. Then you can copy your Perl libraries and built Koha into the final image. That should also help you cut down on the number of layers you have. > > Nice work identifying those system perl dependencies. I keep thinking how we should minimize those. It should be reasonably easy to fix those. > > Actually, if Koha and its Perl dependencies are localized, you could override those with a mounted volume... which makes me wonder why you couldn't use a more minimal Linux... > > I've actually been meaning to make some OpenSUSE Koha images which would help test out the concept of a minimal Koha running on something other than Debian as well, although one may as well use Debian, since that's the supported OS for Koha... > > David Cook > Systems Librarian > Prosentient Systems > 72/330 Wattle St > Ultimo, NSW 2007 > Australia > > Office: 02 9212 0899 > Direct: 02 8005 0595 > > -----Original Message----- > From: Koha-devel On > Behalf Of Julian Maurice > Sent: Tuesday, 18 February 2020 4:59 AM > To: koha-devel > Subject: [Koha-devel] Minimal docker images for Koha > > Hi all, > > I've been playing with docker lately, and I tried to build a minimal docker image for Koha. Here are the results. > > My goals were: > * Install only required "things" to get Koha up and running, and > nothing else (no testing or dev tools), > * No external dependencies except CPAN > * Follow Docker best practices as much as possible > > The resulting images are here: > https://hub.docker.com/repository/docker/julianmaurice/koha > > and the Dockerfiles are here: > https://github.com/jajm/koha-docker > > A few things worth mentioning: > > * I tried to build the smallest image possible by using alpine or perl > slim images at first but it was not that great, because the perl > version shipped with those images is missing some libs, which cause > MARC::Charset to build a database of several hundreds MBs (which is > only 5MBs with a standard perl version). So I chose a more standard > image > (debian:buster) as base. > > * Koha doesn't work well when running with a perl version different than the system perl installed in /usr/bin/perl. For example, the updatedatabase doesn't work when called from the web installer. This is because Perl scripts are called directly as executable files, and shebangs contain '/usr/bin/perl'. Same problem from misc/translator/translate which calls tmpl_process3.pl. > > * I tried to make the Koha installation as self-contained as possible. > Almost everything is installed as a non-root user in /home/koha, including Perl dependencies. > > * It doesn't need a reverse proxy such as apache or nginx. The necessary URL rewriting is handled in PSGI file. The container expose two ports, one for intranet, the other one for OPAC. > > * Each Perl dependency is installed in its latest version, so expect things to break. I can only confirm that the webinstaller, basic cataloguing and search/indexation work. I did not test anything else. > > * There are docker-compose.yml files in the github repository to get Koha running quickly with mariadb, memcached and elasticsearch. > > * Zebra is not installed > > * Images weigh ~1.15GB uncompressed (koha sources included) > > If you made it this far, thanks for reading :) And if you want to use > these docker images, you should start by reading > https://github.com/jajm/koha-docker/blob/master/README.md > > -- > Julian Maurice > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ git : > http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ > -- Julian Maurice BibLibre -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From julian.maurice at biblibre.com Tue Feb 18 08:29:04 2020 From: julian.maurice at biblibre.com (Julian Maurice) Date: Tue, 18 Feb 2020 08:29:04 +0100 Subject: [Koha-devel] Minimal docker images for Koha In-Reply-To: <027401d5e624$ce159630$6a40c290$@prosentient.com.au> References: <021f01d5e5f1$e16be000$a443a000$@prosentient.com.au> <6b76f520-ead4-e215-4c74-e2c90f717e39@biblibre.com> <027401d5e624$ce159630$6a40c290$@prosentient.com.au> Message-ID: <20200218082904.34363c8d@pegasus> Le Tue, 18 Feb 2020 17:29:42 +1100, a écrit : > I was actually wondering earlier how many packaged dependencies Koha > really has. Off the top of my head, I think the main ones are Apache > httpd, Zebra/YAZ, and Mysql client libraries. It looks like "unzip" > is needed as well. A number of the other dependencies like > xmlstarlet, tinymce, libjs-jquery, mysql, etc are just for the Debian > packages. (Actually, I think there is a mysql client binary use in > one of the unit tests which seems suboptimal.) Oh, and due to your > use of that static file middleware, Apache httpd isn't even needed. A > person could probably run the Zebra server in a different container, > share a mounted volume for the data, and then just have Zebra/yaz > client software in the Koha container. Or if you went the > Elasticsearch route, you wouldn't need Zebra at all, right? So in > theory you could maybe get away just with "unzip" as a dependency > that needs installing via a package manager? (Technically, we could > use pure Perl unzip modules as well...) What is unzip needed for ? I didn't think of volumes for Zebra. That's a great idea. I might try that later. From dcook at prosentient.com.au Tue Feb 18 10:09:39 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Tue, 18 Feb 2020 20:09:39 +1100 Subject: [Koha-devel] Minimal docker images for Koha In-Reply-To: <20200218082904.34363c8d@pegasus> References: <021f01d5e5f1$e16be000$a443a000$@prosentient.com.au> <6b76f520-ead4-e215-4c74-e2c90f717e39@biblibre.com> <027401d5e624$ce159630$6a40c290$@prosentient.com.au> <20200218082904.34363c8d@pegasus> Message-ID: <02b501d5e63b$25f5eab0$71e1c010$@prosentient.com.au> "unzip" is used for C4/ImportExportFramework.pm, tools/picture-upload.pl, and tools/upload-cover-image.pl. Ohhhh ./plugins/plugins-upload.pl uses Archive::Extract! Very interesting. There might be merit to not using a pure Perl implementation for pictures, as they may not be as performant as the "unzip" binary. C4/ImportExportFramework.pm probably could use Archive::Extract though. (Archive::Extract also has an option for using "unzip" as a backend I think, so that could be a togglable thing...) Cool! Let us know how you go! It's something I've thought about but hadn't gotten around to trying. I've been thinking about how we could separate out the Zebra server code from the Koha code and package it separately as well. It could help ease the transition to Elasticsearch if Koha just had Zebra client code. (Now that I think about it, there's no reason the Zebra indexing client code even needs to be on the same server as Koha. It just needs database and Zebra access. The only thing Koha really needs is Zebra query client code and configuration.) David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -----Original Message----- From: Julian Maurice Sent: Tuesday, 18 February 2020 6:29 PM To: dcook at prosentient.com.au Cc: 'koha-devel' Subject: Re: [Koha-devel] Minimal docker images for Koha Le Tue, 18 Feb 2020 17:29:42 +1100, a écrit : > I was actually wondering earlier how many packaged dependencies Koha > really has. Off the top of my head, I think the main ones are Apache > httpd, Zebra/YAZ, and Mysql client libraries. It looks like "unzip" > is needed as well. A number of the other dependencies like xmlstarlet, > tinymce, libjs-jquery, mysql, etc are just for the Debian packages. > (Actually, I think there is a mysql client binary use in one of the > unit tests which seems suboptimal.) Oh, and due to your use of that > static file middleware, Apache httpd isn't even needed. A person could > probably run the Zebra server in a different container, share a > mounted volume for the data, and then just have Zebra/yaz client > software in the Koha container. Or if you went the Elasticsearch > route, you wouldn't need Zebra at all, right? So in theory you could > maybe get away just with "unzip" as a dependency that needs installing > via a package manager? (Technically, we could use pure Perl unzip > modules as well...) What is unzip needed for ? I didn't think of volumes for Zebra. That's a great idea. I might try that later. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From kyle.m.hall at gmail.com Tue Feb 18 12:43:04 2020 From: kyle.m.hall at gmail.com (Kyle Hall) Date: Tue, 18 Feb 2020 06:43:04 -0500 Subject: [Koha-devel] Minimal docker images for Koha In-Reply-To: References: Message-ID: This is fantastic Julian! The only thing I can contribute that hasn't already been said by you or David is to suggest taking a look at MiniDeb as a base image ( https://github.com/bitnami/minideb ). I would also suggest using quay.io to build and host your Docker images, as it has built in security scanning. I prefer minimal install images not for size reduction ( though it is nice ), but for the smaller attack surface they provide. Fewer things installed means fewer exploits available! Kyle --- http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) On Mon, Feb 17, 2020 at 12:59 PM Julian Maurice wrote: > Hi all, > > I've been playing with docker lately, and I tried to build a minimal > docker image for Koha. Here are the results. > > My goals were: > * Install only required "things" to get Koha up and running, and nothing > else (no testing or dev tools), > * No external dependencies except CPAN > * Follow Docker best practices as much as possible > > The resulting images are here: > https://hub.docker.com/repository/docker/julianmaurice/koha > > and the Dockerfiles are here: > https://github.com/jajm/koha-docker > > A few things worth mentioning: > > * I tried to build the smallest image possible by using alpine or perl > slim images at first but it was not that great, because the perl version > shipped with those images is missing some libs, which cause > MARC::Charset to build a database of several hundreds MBs (which is only > 5MBs with a standard perl version). So I chose a more standard image > (debian:buster) as base. > > * Koha doesn't work well when running with a perl version different than > the system perl installed in /usr/bin/perl. For example, the > updatedatabase doesn't work when called from the web installer. This is > because Perl scripts are called directly as executable files, and > shebangs contain '/usr/bin/perl'. Same problem from > misc/translator/translate which calls tmpl_process3.pl. > > * I tried to make the Koha installation as self-contained as possible. > Almost everything is installed as a non-root user in /home/koha, > including Perl dependencies. > > * It doesn't need a reverse proxy such as apache or nginx. The necessary > URL rewriting is handled in PSGI file. The container expose two ports, > one for intranet, the other one for OPAC. > > * Each Perl dependency is installed in its latest version, so expect > things to break. I can only confirm that the webinstaller, basic > cataloguing and search/indexation work. I did not test anything else. > > * There are docker-compose.yml files in the github repository to get > Koha running quickly with mariadb, memcached and elasticsearch. > > * Zebra is not installed > > * Images weigh ~1.15GB uncompressed (koha sources included) > > If you made it this far, thanks for reading :) > And if you want to use these docker images, you should start by reading > https://github.com/jajm/koha-docker/blob/master/README.md > > -- > Julian Maurice > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kyle.m.hall at gmail.com Tue Feb 18 12:45:31 2020 From: kyle.m.hall at gmail.com (Kyle Hall) Date: Tue, 18 Feb 2020 06:45:31 -0500 Subject: [Koha-devel] Minimal docker images for Koha In-Reply-To: References: Message-ID: One other question, how does this handle scripts that Koha specifically does not execute using plack? Kyle --- http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) On Tue, Feb 18, 2020 at 6:43 AM Kyle Hall wrote: > This is fantastic Julian! The only thing I can contribute that hasn't > already been said by you or David is to suggest taking a look at MiniDeb as > a base image ( https://github.com/bitnami/minideb ). I would also suggest > using quay.io to build and host your Docker images, as it has built in > security scanning. I prefer minimal install images not for size reduction ( > though it is nice ), but for the smaller attack surface they provide. Fewer > things installed means fewer exploits available! > > Kyle > > --- > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > Crawford County Federated Library System ( http://www.ccfls.org ) > > > On Mon, Feb 17, 2020 at 12:59 PM Julian Maurice < > julian.maurice at biblibre.com> wrote: > >> Hi all, >> >> I've been playing with docker lately, and I tried to build a minimal >> docker image for Koha. Here are the results. >> >> My goals were: >> * Install only required "things" to get Koha up and running, and nothing >> else (no testing or dev tools), >> * No external dependencies except CPAN >> * Follow Docker best practices as much as possible >> >> The resulting images are here: >> https://hub.docker.com/repository/docker/julianmaurice/koha >> >> and the Dockerfiles are here: >> https://github.com/jajm/koha-docker >> >> A few things worth mentioning: >> >> * I tried to build the smallest image possible by using alpine or perl >> slim images at first but it was not that great, because the perl version >> shipped with those images is missing some libs, which cause >> MARC::Charset to build a database of several hundreds MBs (which is only >> 5MBs with a standard perl version). So I chose a more standard image >> (debian:buster) as base. >> >> * Koha doesn't work well when running with a perl version different than >> the system perl installed in /usr/bin/perl. For example, the >> updatedatabase doesn't work when called from the web installer. This is >> because Perl scripts are called directly as executable files, and >> shebangs contain '/usr/bin/perl'. Same problem from >> misc/translator/translate which calls tmpl_process3.pl. >> >> * I tried to make the Koha installation as self-contained as possible. >> Almost everything is installed as a non-root user in /home/koha, >> including Perl dependencies. >> >> * It doesn't need a reverse proxy such as apache or nginx. The necessary >> URL rewriting is handled in PSGI file. The container expose two ports, >> one for intranet, the other one for OPAC. >> >> * Each Perl dependency is installed in its latest version, so expect >> things to break. I can only confirm that the webinstaller, basic >> cataloguing and search/indexation work. I did not test anything else. >> >> * There are docker-compose.yml files in the github repository to get >> Koha running quickly with mariadb, memcached and elasticsearch. >> >> * Zebra is not installed >> >> * Images weigh ~1.15GB uncompressed (koha sources included) >> >> If you made it this far, thanks for reading :) >> And if you want to use these docker images, you should start by reading >> https://github.com/jajm/koha-docker/blob/master/README.md >> >> -- >> Julian Maurice >> BibLibre >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From julian.maurice at biblibre.com Tue Feb 18 13:11:23 2020 From: julian.maurice at biblibre.com (Julian Maurice) Date: Tue, 18 Feb 2020 13:11:23 +0100 Subject: [Koha-devel] Minimal docker images for Koha In-Reply-To: References: Message-ID: <9ed949eb-a716-589e-6b48-2b8daa2bd25f@biblibre.com> Are you talking about these files https://github.com/Koha-Community/Koha/blob/master/debian/templates/apache-shared-intranet-plack.conf#L14-L21 ? I did nothing specific, so they are probably broken :) Le 18/02/2020 à 12:45, Kyle Hall a écrit : > One other question, how does this handle scripts that Koha specifically > does not execute using plack? > > Kyle > > --- > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > Crawford County Federated Library System ( http://www.ccfls.org ) > > > On Tue, Feb 18, 2020 at 6:43 AM Kyle Hall > wrote: > > This is fantastic Julian! The only thing I can contribute that > hasn't already been said by you or David is to suggest taking a look > at MiniDeb as a base image ( https://github.com/bitnami/minideb ). I > would also suggest using quay.io to build and host > your Docker images, as it has built in security scanning. I prefer > minimal install images not for size reduction ( though it is nice ), > but for the smaller attack surface they provide. Fewer things > installed means fewer exploits available! > > Kyle > > --- > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > Crawford County Federated Library System ( http://www.ccfls.org ) > > > On Mon, Feb 17, 2020 at 12:59 PM Julian Maurice > > > wrote: > > Hi all, > > I've been playing with docker lately, and I tried to build a > minimal > docker image for Koha. Here are the results. > > My goals were: > * Install only required "things" to get Koha up and running, and > nothing > else (no testing or dev tools), > * No external dependencies except CPAN > * Follow Docker best practices as much as possible > > The resulting images are here: > https://hub.docker.com/repository/docker/julianmaurice/koha > > and the Dockerfiles are here: > https://github.com/jajm/koha-docker > > A few things worth mentioning: > > * I tried to build the smallest image possible by using alpine > or perl > slim images at first but it was not that great, because the perl > version > shipped with those images is missing some libs, which cause > MARC::Charset to build a database of several hundreds MBs (which > is only > 5MBs with a standard perl version). So I chose a more standard > image > (debian:buster) as base. > > * Koha doesn't work well when running with a perl version > different than > the system perl installed in /usr/bin/perl. For example, the > updatedatabase doesn't work when called from the web installer. > This is > because Perl scripts are called directly as executable files, and > shebangs contain '/usr/bin/perl'. Same problem from > misc/translator/translate which calls tmpl_process3.pl > . > > * I tried to make the Koha installation as self-contained as > possible. > Almost everything is installed as a non-root user in /home/koha, > including Perl dependencies. > > * It doesn't need a reverse proxy such as apache or nginx. The > necessary > URL rewriting is handled in PSGI file. The container expose two > ports, > one for intranet, the other one for OPAC. > > * Each Perl dependency is installed in its latest version, so > expect > things to break. I can only confirm that the webinstaller, basic > cataloguing and search/indexation work. I did not test anything > else. > > * There are docker-compose.yml files in the github repository to > get > Koha running quickly with mariadb, memcached and elasticsearch. > > * Zebra is not installed > > * Images weigh ~1.15GB uncompressed (koha sources included) > > If you made it this far, thanks for reading :) > And if you want to use these docker images, you should start by > reading > https://github.com/jajm/koha-docker/blob/master/README.md > > -- > Julian Maurice > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -- Julian Maurice BibLibre From julian.maurice at biblibre.com Tue Feb 18 13:46:01 2020 From: julian.maurice at biblibre.com (Julian Maurice) Date: Tue, 18 Feb 2020 13:46:01 +0100 Subject: [Koha-devel] Minimal docker images for Koha In-Reply-To: References: Message-ID: I just tried minideb, the resulting image weigh 1.1GB, right between debian:buster-slim and debian:buster I did not found a free plan for quay.io (only a 30-day free trial). Does it have one ? Le 18/02/2020 à 12:43, Kyle Hall a écrit : > This is fantastic Julian! The only thing I can contribute that hasn't > already been said by you or David is to suggest taking a look at MiniDeb > as a base image ( https://github.com/bitnami/minideb ). I would also > suggest using quay.io to build and host your Docker > images, as it has built in security scanning. I prefer minimal install > images not for size reduction ( though it is nice ), but for the smaller > attack surface they provide. Fewer things installed means fewer exploits > available! > > Kyle > > --- > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > Crawford County Federated Library System ( http://www.ccfls.org ) > > > On Mon, Feb 17, 2020 at 12:59 PM Julian Maurice > > wrote: > > Hi all, > > I've been playing with docker lately, and I tried to build a minimal > docker image for Koha. Here are the results. > > My goals were: > * Install only required "things" to get Koha up and running, and > nothing > else (no testing or dev tools), > * No external dependencies except CPAN > * Follow Docker best practices as much as possible > > The resulting images are here: > https://hub.docker.com/repository/docker/julianmaurice/koha > > and the Dockerfiles are here: > https://github.com/jajm/koha-docker > > A few things worth mentioning: > > * I tried to build the smallest image possible by using alpine or perl > slim images at first but it was not that great, because the perl > version > shipped with those images is missing some libs, which cause > MARC::Charset to build a database of several hundreds MBs (which is > only > 5MBs with a standard perl version). So I chose a more standard image > (debian:buster) as base. > > * Koha doesn't work well when running with a perl version different > than > the system perl installed in /usr/bin/perl. For example, the > updatedatabase doesn't work when called from the web installer. This is > because Perl scripts are called directly as executable files, and > shebangs contain '/usr/bin/perl'. Same problem from > misc/translator/translate which calls tmpl_process3.pl > . > > * I tried to make the Koha installation as self-contained as possible. > Almost everything is installed as a non-root user in /home/koha, > including Perl dependencies. > > * It doesn't need a reverse proxy such as apache or nginx. The > necessary > URL rewriting is handled in PSGI file. The container expose two ports, > one for intranet, the other one for OPAC. > > * Each Perl dependency is installed in its latest version, so expect > things to break. I can only confirm that the webinstaller, basic > cataloguing and search/indexation work. I did not test anything else. > > * There are docker-compose.yml files in the github repository to get > Koha running quickly with mariadb, memcached and elasticsearch. > > * Zebra is not installed > > * Images weigh ~1.15GB uncompressed (koha sources included) > > If you made it this far, thanks for reading :) > And if you want to use these docker images, you should start by reading > https://github.com/jajm/koha-docker/blob/master/README.md > > -- > Julian Maurice > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -- Julian Maurice BibLibre From kyle.m.hall at gmail.com Tue Feb 18 22:07:57 2020 From: kyle.m.hall at gmail.com (Kyle Hall) Date: Tue, 18 Feb 2020 16:07:57 -0500 Subject: [Koha-devel] Minimal docker images for Koha In-Reply-To: References: Message-ID: They don’t make it easy to understand, all you need to do is create your account and when you go to add a repository you can choose a Public GitHub repository and you will not need any kind of paid account. On Tue, Feb 18, 2020 at 7:46 AM Julian Maurice wrote: > I just tried minideb, the resulting image weigh 1.1GB, right between > debian:buster-slim and debian:buster > > I did not found a free plan for quay.io (only a 30-day free trial). Does > it have one ? > > Le 18/02/2020 à 12:43, Kyle Hall a écrit : > > This is fantastic Julian! The only thing I can contribute that hasn't > > already been said by you or David is to suggest taking a look at MiniDeb > > as a base image ( https://github.com/bitnami/minideb ). I would also > > suggest using quay.io to build and host your Docker > > images, as it has built in security scanning. I prefer minimal install > > images not for size reduction ( though it is nice ), but for the smaller > > attack surface they provide. Fewer things installed means fewer exploits > > available! > > > > Kyle > > > > --- > > http://www.kylehall.info > > ByWater Solutions ( http://bywatersolutions.com ) > > Meadville Public Library ( http://www.meadvillelibrary.org ) > > Crawford County Federated Library System ( http://www.ccfls.org ) > > > > > > On Mon, Feb 17, 2020 at 12:59 PM Julian Maurice > > > > wrote: > > > > Hi all, > > > > I've been playing with docker lately, and I tried to build a minimal > > docker image for Koha. Here are the results. > > > > My goals were: > > * Install only required "things" to get Koha up and running, and > > nothing > > else (no testing or dev tools), > > * No external dependencies except CPAN > > * Follow Docker best practices as much as possible > > > > The resulting images are here: > > https://hub.docker.com/repository/docker/julianmaurice/koha > > > > and the Dockerfiles are here: > > https://github.com/jajm/koha-docker > > > > A few things worth mentioning: > > > > * I tried to build the smallest image possible by using alpine or > perl > > slim images at first but it was not that great, because the perl > > version > > shipped with those images is missing some libs, which cause > > MARC::Charset to build a database of several hundreds MBs (which is > > only > > 5MBs with a standard perl version). So I chose a more standard image > > (debian:buster) as base. > > > > * Koha doesn't work well when running with a perl version different > > than > > the system perl installed in /usr/bin/perl. For example, the > > updatedatabase doesn't work when called from the web installer. This > is > > because Perl scripts are called directly as executable files, and > > shebangs contain '/usr/bin/perl'. Same problem from > > misc/translator/translate which calls tmpl_process3.pl > > . > > > > * I tried to make the Koha installation as self-contained as > possible. > > Almost everything is installed as a non-root user in /home/koha, > > including Perl dependencies. > > > > * It doesn't need a reverse proxy such as apache or nginx. The > > necessary > > URL rewriting is handled in PSGI file. The container expose two > ports, > > one for intranet, the other one for OPAC. > > > > * Each Perl dependency is installed in its latest version, so expect > > things to break. I can only confirm that the webinstaller, basic > > cataloguing and search/indexation work. I did not test anything else. > > > > * There are docker-compose.yml files in the github repository to get > > Koha running quickly with mariadb, memcached and elasticsearch. > > > > * Zebra is not installed > > > > * Images weigh ~1.15GB uncompressed (koha sources included) > > > > If you made it this far, thanks for reading :) > > And if you want to use these docker images, you should start by > reading > > https://github.com/jajm/koha-docker/blob/master/README.md > > > > -- > > Julian Maurice > > BibLibre > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at lists.koha-community.org > > > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ > > git : http://git.koha-community.org/ > > bugs : http://bugs.koha-community.org/ > > > > -- > Julian Maurice > BibLibre > -- --- http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Wed Feb 19 01:17:48 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Wed, 19 Feb 2020 11:17:48 +1100 Subject: [Koha-devel] Minimal docker images for Koha In-Reply-To: References: Message-ID: <030f01d5e6ba$0401f3c0$0c05db40$@prosentient.com.au> Mmm that’s a good point. The smaller attack surface is something I harp on about a lot when it comes to making minimal images. That’s actually led me down some very fun rabbit holes about operating systems and Linux in particular. For instance, here’s the Dockerfile for ubuntu:latest. It’s actually quite minimal with the majority of the work being done by “ADD ubuntu-bionic-core-cloudimg-amd64-root.tar.gz /”, which can be found at https://partner-images.canonical.com/core/bionic/current/ubuntu-bionic-core-cloudimg-amd64-root.tar.gz. When you open that up, it’s just a small Ubuntu root file system. Now what does that get us? First I’ll backtrack. When the host boots, GRUB 2 finds the desired Linux kernel, loads the kernel and the initramfs, and then transfers control to the kernel, which runs the initramfs’s /init script (which typically invokes systemd these days). That /init script finds the “real” root file system, mounts it, and then executes systemd on the real root file system, which acts as the init system and becomes our old faithful PID 1. Obviously that process doesn’t correspond to a container’s lifecycle. When a container is started, the kernel is already running and the root file system is already mounted. There’s already kernel mode and user mode code running to manage the computer. Docker gives us isolation using Linux kernel features like cgroups and namespaces, and takes care of special file system cases like /dev, /proc/, and /sys for us. So a person doesn’t need a whole OS file system just to run a single program in Docker. However, in our case, it gets complicated quickly, since Koha needs MySQL client libraries, Zebra client libraries, and whatever other libraries and files our Perl modules need (DateTime leverages OS-level datetime files I think, there’s libxml, probably GD, etc.). If we were really thorough, we probably could get Koha running in a very minimal container, but it would take some work. It could be fun though. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Koha-devel On Behalf Of Kyle Hall Sent: Tuesday, 18 February 2020 10:43 PM To: Julian Maurice Cc: koha-devel Subject: Re: [Koha-devel] Minimal docker images for Koha This is fantastic Julian! The only thing I can contribute that hasn't already been said by you or David is to suggest taking a look at MiniDeb as a base image ( https://github.com/bitnami/minideb ). I would also suggest using quay.io to build and host your Docker images, as it has built in security scanning. I prefer minimal install images not for size reduction ( though it is nice ), but for the smaller attack surface they provide. Fewer things installed means fewer exploits available! Kyle --- http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) On Mon, Feb 17, 2020 at 12:59 PM Julian Maurice > wrote: Hi all, I've been playing with docker lately, and I tried to build a minimal docker image for Koha. Here are the results. My goals were: * Install only required "things" to get Koha up and running, and nothing else (no testing or dev tools), * No external dependencies except CPAN * Follow Docker best practices as much as possible The resulting images are here: https://hub.docker.com/repository/docker/julianmaurice/koha and the Dockerfiles are here: https://github.com/jajm/koha-docker A few things worth mentioning: * I tried to build the smallest image possible by using alpine or perl slim images at first but it was not that great, because the perl version shipped with those images is missing some libs, which cause MARC::Charset to build a database of several hundreds MBs (which is only 5MBs with a standard perl version). So I chose a more standard image (debian:buster) as base. * Koha doesn't work well when running with a perl version different than the system perl installed in /usr/bin/perl. For example, the updatedatabase doesn't work when called from the web installer. This is because Perl scripts are called directly as executable files, and shebangs contain '/usr/bin/perl'. Same problem from misc/translator/translate which calls tmpl_process3.pl . * I tried to make the Koha installation as self-contained as possible. Almost everything is installed as a non-root user in /home/koha, including Perl dependencies. * It doesn't need a reverse proxy such as apache or nginx. The necessary URL rewriting is handled in PSGI file. The container expose two ports, one for intranet, the other one for OPAC. * Each Perl dependency is installed in its latest version, so expect things to break. I can only confirm that the webinstaller, basic cataloguing and search/indexation work. I did not test anything else. * There are docker-compose.yml files in the github repository to get Koha running quickly with mariadb, memcached and elasticsearch. * Zebra is not installed * Images weigh ~1.15GB uncompressed (koha sources included) If you made it this far, thanks for reading :) And if you want to use these docker images, you should start by reading https://github.com/jajm/koha-docker/blob/master/README.md -- Julian Maurice BibLibre _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From dcook at prosentient.com.au Wed Feb 19 01:21:03 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Wed, 19 Feb 2020 11:21:03 +1100 Subject: [Koha-devel] Minimal docker images for Koha In-Reply-To: <9ed949eb-a716-589e-6b48-2b8daa2bd25f@biblibre.com> References: <9ed949eb-a716-589e-6b48-2b8daa2bd25f@biblibre.com> Message-ID: <032001d5e6ba$78a7dc30$69f79490$@prosentient.com.au> Funny I was just looking at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15032. One of these days we should push forward more on queues: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -----Original Message----- From: Koha-devel On Behalf Of Julian Maurice Sent: Tuesday, 18 February 2020 11:11 PM To: Kyle Hall Cc: koha-devel Subject: Re: [Koha-devel] Minimal docker images for Koha Are you talking about these files https://github.com/Koha-Community/Koha/blob/master/debian/templates/apache-shared-intranet-plack.conf#L14-L21 ? I did nothing specific, so they are probably broken :) Le 18/02/2020 à 12:45, Kyle Hall a écrit : > One other question, how does this handle scripts that Koha > specifically does not execute using plack? > > Kyle > > --- > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) Meadville Public > Library ( http://www.meadvillelibrary.org ) Crawford County Federated > Library System ( http://www.ccfls.org ) > > > On Tue, Feb 18, 2020 at 6:43 AM Kyle Hall > wrote: > > This is fantastic Julian! The only thing I can contribute that > hasn't already been said by you or David is to suggest taking a look > at MiniDeb as a base image ( https://github.com/bitnami/minideb ). I > would also suggest using quay.io to build and host > your Docker images, as it has built in security scanning. I prefer > minimal install images not for size reduction ( though it is nice ), > but for the smaller attack surface they provide. Fewer things > installed means fewer exploits available! > > Kyle > > --- > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > Crawford County Federated Library System ( http://www.ccfls.org ) > > > On Mon, Feb 17, 2020 at 12:59 PM Julian Maurice > > > wrote: > > Hi all, > > I've been playing with docker lately, and I tried to build a > minimal > docker image for Koha. Here are the results. > > My goals were: > * Install only required "things" to get Koha up and running, and > nothing > else (no testing or dev tools), > * No external dependencies except CPAN > * Follow Docker best practices as much as possible > > The resulting images are here: > https://hub.docker.com/repository/docker/julianmaurice/koha > > and the Dockerfiles are here: > https://github.com/jajm/koha-docker > > A few things worth mentioning: > > * I tried to build the smallest image possible by using alpine > or perl > slim images at first but it was not that great, because the perl > version > shipped with those images is missing some libs, which cause > MARC::Charset to build a database of several hundreds MBs (which > is only > 5MBs with a standard perl version). So I chose a more standard > image > (debian:buster) as base. > > * Koha doesn't work well when running with a perl version > different than > the system perl installed in /usr/bin/perl. For example, the > updatedatabase doesn't work when called from the web installer. > This is > because Perl scripts are called directly as executable files, and > shebangs contain '/usr/bin/perl'. Same problem from > misc/translator/translate which calls tmpl_process3.pl > . > > * I tried to make the Koha installation as self-contained as > possible. > Almost everything is installed as a non-root user in /home/koha, > including Perl dependencies. > > * It doesn't need a reverse proxy such as apache or nginx. The > necessary > URL rewriting is handled in PSGI file. The container expose two > ports, > one for intranet, the other one for OPAC. > > * Each Perl dependency is installed in its latest version, so > expect > things to break. I can only confirm that the webinstaller, basic > cataloguing and search/indexation work. I did not test anything > else. > > * There are docker-compose.yml files in the github repository to > get > Koha running quickly with mariadb, memcached and elasticsearch. > > * Zebra is not installed > > * Images weigh ~1.15GB uncompressed (koha sources included) > > If you made it this far, thanks for reading :) > And if you want to use these docker images, you should start by > reading > https://github.com/jajm/koha-docker/blob/master/README.md > > -- > Julian Maurice > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -- Julian Maurice BibLibre _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From kyle.m.hall at gmail.com Wed Feb 19 14:03:32 2020 From: kyle.m.hall at gmail.com (Kyle Hall) Date: Wed, 19 Feb 2020 08:03:32 -0500 Subject: [Koha-devel] Minimal docker images for Koha In-Reply-To: <032001d5e6ba$78a7dc30$69f79490$@prosentient.com.au> References: <9ed949eb-a716-589e-6b48-2b8daa2bd25f@biblibre.com> <032001d5e6ba$78a7dc30$69f79490$@prosentient.com.au> Message-ID: Agreed! I think a task queue would be a huge benefit to Koha, we have so many long running batch operations. Kyle --- http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) On Tue, Feb 18, 2020 at 7:21 PM wrote: > Funny I was just looking at > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15032. > > One of these days we should push forward more on queues: > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417. > > David Cook > Systems Librarian > Prosentient Systems > 72/330 Wattle St > Ultimo, NSW 2007 > Australia > > Office: 02 9212 0899 > Direct: 02 8005 0595 > > -----Original Message----- > From: Koha-devel On Behalf > Of Julian Maurice > Sent: Tuesday, 18 February 2020 11:11 PM > To: Kyle Hall > Cc: koha-devel > Subject: Re: [Koha-devel] Minimal docker images for Koha > > Are you talking about these files > > https://github.com/Koha-Community/Koha/blob/master/debian/templates/apache-shared-intranet-plack.conf#L14-L21 > ? > > I did nothing specific, so they are probably broken :) > > Le 18/02/2020 à 12:45, Kyle Hall a écrit : > > One other question, how does this handle scripts that Koha > > specifically does not execute using plack? > > > > Kyle > > > > --- > > http://www.kylehall.info > > ByWater Solutions ( http://bywatersolutions.com ) Meadville Public > > Library ( http://www.meadvillelibrary.org ) Crawford County Federated > > Library System ( http://www.ccfls.org ) > > > > > > On Tue, Feb 18, 2020 at 6:43 AM Kyle Hall > > wrote: > > > > This is fantastic Julian! The only thing I can contribute that > > hasn't already been said by you or David is to suggest taking a look > > at MiniDeb as a base image ( https://github.com/bitnami/minideb ). I > > would also suggest using quay.io to build and host > > your Docker images, as it has built in security scanning. I prefer > > minimal install images not for size reduction ( though it is nice ), > > but for the smaller attack surface they provide. Fewer things > > installed means fewer exploits available! > > > > Kyle > > > > --- > > http://www.kylehall.info > > ByWater Solutions ( http://bywatersolutions.com ) > > Meadville Public Library ( http://www.meadvillelibrary.org ) > > Crawford County Federated Library System ( http://www.ccfls.org ) > > > > > > On Mon, Feb 17, 2020 at 12:59 PM Julian Maurice > > > > > wrote: > > > > Hi all, > > > > I've been playing with docker lately, and I tried to build a > > minimal > > docker image for Koha. Here are the results. > > > > My goals were: > > * Install only required "things" to get Koha up and running, and > > nothing > > else (no testing or dev tools), > > * No external dependencies except CPAN > > * Follow Docker best practices as much as possible > > > > The resulting images are here: > > https://hub.docker.com/repository/docker/julianmaurice/koha > > > > and the Dockerfiles are here: > > https://github.com/jajm/koha-docker > > > > A few things worth mentioning: > > > > * I tried to build the smallest image possible by using alpine > > or perl > > slim images at first but it was not that great, because the perl > > version > > shipped with those images is missing some libs, which cause > > MARC::Charset to build a database of several hundreds MBs (which > > is only > > 5MBs with a standard perl version). So I chose a more standard > > image > > (debian:buster) as base. > > > > * Koha doesn't work well when running with a perl version > > different than > > the system perl installed in /usr/bin/perl. For example, the > > updatedatabase doesn't work when called from the web installer. > > This is > > because Perl scripts are called directly as executable files, and > > shebangs contain '/usr/bin/perl'. Same problem from > > misc/translator/translate which calls tmpl_process3.pl > > . > > > > * I tried to make the Koha installation as self-contained as > > possible. > > Almost everything is installed as a non-root user in /home/koha, > > including Perl dependencies. > > > > * It doesn't need a reverse proxy such as apache or nginx. The > > necessary > > URL rewriting is handled in PSGI file. The container expose two > > ports, > > one for intranet, the other one for OPAC. > > > > * Each Perl dependency is installed in its latest version, so > > expect > > things to break. I can only confirm that the webinstaller, basic > > cataloguing and search/indexation work. I did not test anything > > else. > > > > * There are docker-compose.yml files in the github repository to > > get > > Koha running quickly with mariadb, memcached and elasticsearch. > > > > * Zebra is not installed > > > > * Images weigh ~1.15GB uncompressed (koha sources included) > > > > If you made it this far, thanks for reading :) > > And if you want to use these docker images, you should start by > > reading > > https://github.com/jajm/koha-docker/blob/master/README.md > > > > -- > > Julian Maurice > > BibLibre > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at lists.koha-community.org > > > > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ > > git : http://git.koha-community.org/ > > bugs : http://bugs.koha-community.org/ > > > > -- > Julian Maurice > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ git : > http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From philippe.blouin at inlibro.com Wed Feb 19 15:56:53 2020 From: philippe.blouin at inlibro.com (Philippe Blouin) Date: Wed, 19 Feb 2020 09:56:53 -0500 Subject: [Koha-devel] Looking for QA availability to pass 11299 Message-ID: Good morning/dinner/evening dear Koha developpers, We're looking for a QA to pass 11299.  Jonathan and Cate have removed themselves, and the patch is big and has been rebased already too many times in its 7 years history. This has been by far the costliest development for our sponsor, CCSR/Collecto, that has already given much to the community over 10 years. Bouzid has played by the rules, and has put in every single damn request presented to him by QA/Testers.  Including redoing it from ground up lately to match the ever changing coding requirements and architecture. So, anyone has some time? Regards, -- Philippe Blouin, Directeur de la technologie Tél.  : (833) 465-4276, poste 230 philippe.blouin at inLibro.com inLibro | pour esprit libre | www.inLibro.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Thu Feb 20 04:59:42 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Thu, 20 Feb 2020 14:59:42 +1100 Subject: [Koha-devel] Minimal docker images for Koha In-Reply-To: References: <9ed949eb-a716-589e-6b48-2b8daa2bd25f@biblibre.com> <032001d5e6ba$78a7dc30$69f79490$@prosentient.com.au> Message-ID: <043c01d5e7a2$2e7efc90$8b7cf5b0$@prosentient.com.au> Exactly! I would love to see a task queue based record importer. (I keep thinking about a Koha plugin to provide a web ui for scheduling OAI-PMH harvesting, and then third-party applications that can consume from the task queue, stage the records… probably via the REST API… and then enqueue tasks to a high performance record importer worker…) Are you going to the Hackfest in Marseille? (I wanted to go this year but life is just too hectic this year, although planning to go to Kohacon in October.) A task queue could be a great Hackfest project… David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Kyle Hall Sent: Thursday, 20 February 2020 12:04 AM To: David Cook Cc: Julian Maurice ; koha-devel Subject: Re: [Koha-devel] Minimal docker images for Koha Agreed! I think a task queue would be a huge benefit to Koha, we have so many long running batch operations. Kyle --- http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) On Tue, Feb 18, 2020 at 7:21 PM > wrote: Funny I was just looking at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15032. One of these days we should push forward more on queues: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -----Original Message----- From: Koha-devel > On Behalf Of Julian Maurice Sent: Tuesday, 18 February 2020 11:11 PM To: Kyle Hall > Cc: koha-devel > Subject: Re: [Koha-devel] Minimal docker images for Koha Are you talking about these files https://github.com/Koha-Community/Koha/blob/master/debian/templates/apache-shared-intranet-plack.conf#L14-L21 ? I did nothing specific, so they are probably broken :) Le 18/02/2020 à 12:45, Kyle Hall a écrit : > One other question, how does this handle scripts that Koha > specifically does not execute using plack? > > Kyle > > --- > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) Meadville Public > Library ( http://www.meadvillelibrary.org ) Crawford County Federated > Library System ( http://www.ccfls.org ) > > > On Tue, Feb 18, 2020 at 6:43 AM Kyle Hall > >> wrote: > > This is fantastic Julian! The only thing I can contribute that > hasn't already been said by you or David is to suggest taking a look > at MiniDeb as a base image ( https://github.com/bitnami/minideb ). I > would also suggest using quay.io to build and host > your Docker images, as it has built in security scanning. I prefer > minimal install images not for size reduction ( though it is nice ), > but for the smaller attack surface they provide. Fewer things > installed means fewer exploits available! > > Kyle > > --- > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > Crawford County Federated Library System ( http://www.ccfls.org ) > > > On Mon, Feb 17, 2020 at 12:59 PM Julian Maurice > >> > wrote: > > Hi all, > > I've been playing with docker lately, and I tried to build a > minimal > docker image for Koha. Here are the results. > > My goals were: > * Install only required "things" to get Koha up and running, and > nothing > else (no testing or dev tools), > * No external dependencies except CPAN > * Follow Docker best practices as much as possible > > The resulting images are here: > https://hub.docker.com/repository/docker/julianmaurice/koha > > and the Dockerfiles are here: > https://github.com/jajm/koha-docker > > A few things worth mentioning: > > * I tried to build the smallest image possible by using alpine > or perl > slim images at first but it was not that great, because the perl > version > shipped with those images is missing some libs, which cause > MARC::Charset to build a database of several hundreds MBs (which > is only > 5MBs with a standard perl version). So I chose a more standard > image > (debian:buster) as base. > > * Koha doesn't work well when running with a perl version > different than > the system perl installed in /usr/bin/perl. For example, the > updatedatabase doesn't work when called from the web installer. > This is > because Perl scripts are called directly as executable files, and > shebangs contain '/usr/bin/perl'. Same problem from > misc/translator/translate which calls tmpl_process3.pl > . > > * I tried to make the Koha installation as self-contained as > possible. > Almost everything is installed as a non-root user in /home/koha, > including Perl dependencies. > > * It doesn't need a reverse proxy such as apache or nginx. The > necessary > URL rewriting is handled in PSGI file. The container expose two > ports, > one for intranet, the other one for OPAC. > > * Each Perl dependency is installed in its latest version, so > expect > things to break. I can only confirm that the webinstaller, basic > cataloguing and search/indexation work. I did not test anything > else. > > * There are docker-compose.yml files in the github repository to > get > Koha running quickly with mariadb, memcached and elasticsearch. > > * Zebra is not installed > > * Images weigh ~1.15GB uncompressed (koha sources included) > > If you made it this far, thanks for reading :) > And if you want to use these docker images, you should start by > reading > https://github.com/jajm/koha-docker/blob/master/README.md > > -- > Julian Maurice > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -- Julian Maurice BibLibre _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From jonathan.druart at bugs.koha-community.org Thu Feb 20 08:58:54 2020 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Thu, 20 Feb 2020 08:58:54 +0100 Subject: [Koha-devel] Minimal docker images for Koha In-Reply-To: <043c01d5e7a2$2e7efc90$8b7cf5b0$@prosentient.com.au> References: <9ed949eb-a716-589e-6b48-2b8daa2bd25f@biblibre.com> <032001d5e6ba$78a7dc30$69f79490$@prosentient.com.au> <043c01d5e7a2$2e7efc90$8b7cf5b0$@prosentient.com.au> Message-ID: I am planning to get back to bug 22417 in the days. Le jeu. 20 févr. 2020 à 04:59, a écrit : > > Exactly! I would love to see a task queue based record importer. (I keep thinking about a Koha plugin to provide a web ui for scheduling OAI-PMH harvesting, and then third-party applications that can consume from the task queue, stage the records… probably via the REST API… and then enqueue tasks to a high performance record importer worker…) > > > > Are you going to the Hackfest in Marseille? (I wanted to go this year but life is just too hectic this year, although planning to go to Kohacon in October.) A task queue could be a great Hackfest project… > > > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > Australia > > > > Office: 02 9212 0899 > > Direct: 02 8005 0595 > > > > From: Kyle Hall > Sent: Thursday, 20 February 2020 12:04 AM > To: David Cook > Cc: Julian Maurice ; koha-devel > Subject: Re: [Koha-devel] Minimal docker images for Koha > > > > Agreed! I think a task queue would be a huge benefit to Koha, we have so many long running batch operations. > > > > Kyle > > > > --- > > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > Crawford County Federated Library System ( http://www.ccfls.org ) > > > > > > On Tue, Feb 18, 2020 at 7:21 PM wrote: > > Funny I was just looking at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15032. > > One of these days we should push forward more on queues: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417. > > David Cook > Systems Librarian > Prosentient Systems > 72/330 Wattle St > Ultimo, NSW 2007 > Australia > > Office: 02 9212 0899 > Direct: 02 8005 0595 > > -----Original Message----- > From: Koha-devel On Behalf Of Julian Maurice > Sent: Tuesday, 18 February 2020 11:11 PM > To: Kyle Hall > Cc: koha-devel > Subject: Re: [Koha-devel] Minimal docker images for Koha > > Are you talking about these files > https://github.com/Koha-Community/Koha/blob/master/debian/templates/apache-shared-intranet-plack.conf#L14-L21 > ? > > I did nothing specific, so they are probably broken :) > > Le 18/02/2020 à 12:45, Kyle Hall a écrit : > > One other question, how does this handle scripts that Koha > > specifically does not execute using plack? > > > > Kyle > > > > --- > > http://www.kylehall.info > > ByWater Solutions ( http://bywatersolutions.com ) Meadville Public > > Library ( http://www.meadvillelibrary.org ) Crawford County Federated > > Library System ( http://www.ccfls.org ) > > > > > > On Tue, Feb 18, 2020 at 6:43 AM Kyle Hall > > wrote: > > > > This is fantastic Julian! The only thing I can contribute that > > hasn't already been said by you or David is to suggest taking a look > > at MiniDeb as a base image ( https://github.com/bitnami/minideb ). I > > would also suggest using quay.io to build and host > > your Docker images, as it has built in security scanning. I prefer > > minimal install images not for size reduction ( though it is nice ), > > but for the smaller attack surface they provide. Fewer things > > installed means fewer exploits available! > > > > Kyle > > > > --- > > http://www.kylehall.info > > ByWater Solutions ( http://bywatersolutions.com ) > > Meadville Public Library ( http://www.meadvillelibrary.org ) > > Crawford County Federated Library System ( http://www.ccfls.org ) > > > > > > On Mon, Feb 17, 2020 at 12:59 PM Julian Maurice > > > > > wrote: > > > > Hi all, > > > > I've been playing with docker lately, and I tried to build a > > minimal > > docker image for Koha. Here are the results. > > > > My goals were: > > * Install only required "things" to get Koha up and running, and > > nothing > > else (no testing or dev tools), > > * No external dependencies except CPAN > > * Follow Docker best practices as much as possible > > > > The resulting images are here: > > https://hub.docker.com/repository/docker/julianmaurice/koha > > > > and the Dockerfiles are here: > > https://github.com/jajm/koha-docker > > > > A few things worth mentioning: > > > > * I tried to build the smallest image possible by using alpine > > or perl > > slim images at first but it was not that great, because the perl > > version > > shipped with those images is missing some libs, which cause > > MARC::Charset to build a database of several hundreds MBs (which > > is only > > 5MBs with a standard perl version). So I chose a more standard > > image > > (debian:buster) as base. > > > > * Koha doesn't work well when running with a perl version > > different than > > the system perl installed in /usr/bin/perl. For example, the > > updatedatabase doesn't work when called from the web installer. > > This is > > because Perl scripts are called directly as executable files, and > > shebangs contain '/usr/bin/perl'. Same problem from > > misc/translator/translate which calls tmpl_process3.pl > > . > > > > * I tried to make the Koha installation as self-contained as > > possible. > > Almost everything is installed as a non-root user in /home/koha, > > including Perl dependencies. > > > > * It doesn't need a reverse proxy such as apache or nginx. The > > necessary > > URL rewriting is handled in PSGI file. The container expose two > > ports, > > one for intranet, the other one for OPAC. > > > > * Each Perl dependency is installed in its latest version, so > > expect > > things to break. I can only confirm that the webinstaller, basic > > cataloguing and search/indexation work. I did not test anything > > else. > > > > * There are docker-compose.yml files in the github repository to > > get > > Koha running quickly with mariadb, memcached and elasticsearch. > > > > * Zebra is not installed > > > > * Images weigh ~1.15GB uncompressed (koha sources included) > > > > If you made it this far, thanks for reading :) > > And if you want to use these docker images, you should start by > > reading > > https://github.com/jajm/koha-docker/blob/master/README.md > > > > -- > > Julian Maurice > > BibLibre > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at lists.koha-community.org > > > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ > > git : http://git.koha-community.org/ > > bugs : http://bugs.koha-community.org/ > > > > -- > Julian Maurice > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ From jonathan.druart at bugs.koha-community.org Thu Feb 20 09:08:33 2020 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Thu, 20 Feb 2020 09:08:33 +0100 Subject: [Koha-devel] Minimal docker images for Koha In-Reply-To: References: <9ed949eb-a716-589e-6b48-2b8daa2bd25f@biblibre.com> <032001d5e6ba$78a7dc30$69f79490$@prosentient.com.au> <043c01d5e7a2$2e7efc90$8b7cf5b0$@prosentient.com.au> Message-ID: in the *next* days ;) Le jeu. 20 févr. 2020 à 08:58, Jonathan Druart a écrit : > > I am planning to get back to bug 22417 in the days. > > Le jeu. 20 févr. 2020 à 04:59, a écrit : > > > > Exactly! I would love to see a task queue based record importer. (I keep thinking about a Koha plugin to provide a web ui for scheduling OAI-PMH harvesting, and then third-party applications that can consume from the task queue, stage the records… probably via the REST API… and then enqueue tasks to a high performance record importer worker…) > > > > > > > > Are you going to the Hackfest in Marseille? (I wanted to go this year but life is just too hectic this year, although planning to go to Kohacon in October.) A task queue could be a great Hackfest project… > > > > > > > > David Cook > > > > Systems Librarian > > > > Prosentient Systems > > > > 72/330 Wattle St > > > > Ultimo, NSW 2007 > > > > Australia > > > > > > > > Office: 02 9212 0899 > > > > Direct: 02 8005 0595 > > > > > > > > From: Kyle Hall > > Sent: Thursday, 20 February 2020 12:04 AM > > To: David Cook > > Cc: Julian Maurice ; koha-devel > > Subject: Re: [Koha-devel] Minimal docker images for Koha > > > > > > > > Agreed! I think a task queue would be a huge benefit to Koha, we have so many long running batch operations. > > > > > > > > Kyle > > > > > > > > --- > > > > http://www.kylehall.info > > ByWater Solutions ( http://bywatersolutions.com ) > > Meadville Public Library ( http://www.meadvillelibrary.org ) > > Crawford County Federated Library System ( http://www.ccfls.org ) > > > > > > > > > > > > On Tue, Feb 18, 2020 at 7:21 PM wrote: > > > > Funny I was just looking at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15032. > > > > One of these days we should push forward more on queues: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417. > > > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > Australia > > > > Office: 02 9212 0899 > > Direct: 02 8005 0595 > > > > -----Original Message----- > > From: Koha-devel On Behalf Of Julian Maurice > > Sent: Tuesday, 18 February 2020 11:11 PM > > To: Kyle Hall > > Cc: koha-devel > > Subject: Re: [Koha-devel] Minimal docker images for Koha > > > > Are you talking about these files > > https://github.com/Koha-Community/Koha/blob/master/debian/templates/apache-shared-intranet-plack.conf#L14-L21 > > ? > > > > I did nothing specific, so they are probably broken :) > > > > Le 18/02/2020 à 12:45, Kyle Hall a écrit : > > > One other question, how does this handle scripts that Koha > > > specifically does not execute using plack? > > > > > > Kyle > > > > > > --- > > > http://www.kylehall.info > > > ByWater Solutions ( http://bywatersolutions.com ) Meadville Public > > > Library ( http://www.meadvillelibrary.org ) Crawford County Federated > > > Library System ( http://www.ccfls.org ) > > > > > > > > > On Tue, Feb 18, 2020 at 6:43 AM Kyle Hall > > > wrote: > > > > > > This is fantastic Julian! The only thing I can contribute that > > > hasn't already been said by you or David is to suggest taking a look > > > at MiniDeb as a base image ( https://github.com/bitnami/minideb ). I > > > would also suggest using quay.io to build and host > > > your Docker images, as it has built in security scanning. I prefer > > > minimal install images not for size reduction ( though it is nice ), > > > but for the smaller attack surface they provide. Fewer things > > > installed means fewer exploits available! > > > > > > Kyle > > > > > > --- > > > http://www.kylehall.info > > > ByWater Solutions ( http://bywatersolutions.com ) > > > Meadville Public Library ( http://www.meadvillelibrary.org ) > > > Crawford County Federated Library System ( http://www.ccfls.org ) > > > > > > > > > On Mon, Feb 17, 2020 at 12:59 PM Julian Maurice > > > > > > > wrote: > > > > > > Hi all, > > > > > > I've been playing with docker lately, and I tried to build a > > > minimal > > > docker image for Koha. Here are the results. > > > > > > My goals were: > > > * Install only required "things" to get Koha up and running, and > > > nothing > > > else (no testing or dev tools), > > > * No external dependencies except CPAN > > > * Follow Docker best practices as much as possible > > > > > > The resulting images are here: > > > https://hub.docker.com/repository/docker/julianmaurice/koha > > > > > > and the Dockerfiles are here: > > > https://github.com/jajm/koha-docker > > > > > > A few things worth mentioning: > > > > > > * I tried to build the smallest image possible by using alpine > > > or perl > > > slim images at first but it was not that great, because the perl > > > version > > > shipped with those images is missing some libs, which cause > > > MARC::Charset to build a database of several hundreds MBs (which > > > is only > > > 5MBs with a standard perl version). So I chose a more standard > > > image > > > (debian:buster) as base. > > > > > > * Koha doesn't work well when running with a perl version > > > different than > > > the system perl installed in /usr/bin/perl. For example, the > > > updatedatabase doesn't work when called from the web installer. > > > This is > > > because Perl scripts are called directly as executable files, and > > > shebangs contain '/usr/bin/perl'. Same problem from > > > misc/translator/translate which calls tmpl_process3.pl > > > . > > > > > > * I tried to make the Koha installation as self-contained as > > > possible. > > > Almost everything is installed as a non-root user in /home/koha, > > > including Perl dependencies. > > > > > > * It doesn't need a reverse proxy such as apache or nginx. The > > > necessary > > > URL rewriting is handled in PSGI file. The container expose two > > > ports, > > > one for intranet, the other one for OPAC. > > > > > > * Each Perl dependency is installed in its latest version, so > > > expect > > > things to break. I can only confirm that the webinstaller, basic > > > cataloguing and search/indexation work. I did not test anything > > > else. > > > > > > * There are docker-compose.yml files in the github repository to > > > get > > > Koha running quickly with mariadb, memcached and elasticsearch. > > > > > > * Zebra is not installed > > > > > > * Images weigh ~1.15GB uncompressed (koha sources included) > > > > > > If you made it this far, thanks for reading :) > > > And if you want to use these docker images, you should start by > > > reading > > > https://github.com/jajm/koha-docker/blob/master/README.md > > > > > > -- > > > Julian Maurice > > > BibLibre > > > _______________________________________________ > > > Koha-devel mailing list > > > Koha-devel at lists.koha-community.org > > > > > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > > website : http://www.koha-community.org/ > > > git : http://git.koha-community.org/ > > > bugs : http://bugs.koha-community.org/ > > > > > > > -- > > Julian Maurice > > BibLibre > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at lists.koha-community.org > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ > > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at lists.koha-community.org > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ > > git : http://git.koha-community.org/ > > bugs : http://bugs.koha-community.org/ From julian.maurice at biblibre.com Thu Feb 20 09:26:58 2020 From: julian.maurice at biblibre.com (Julian Maurice) Date: Thu, 20 Feb 2020 09:26:58 +0100 Subject: [Koha-devel] Minimal docker images for Koha In-Reply-To: <030f01d5e6ba$0401f3c0$0c05db40$@prosentient.com.au> References: <030f01d5e6ba$0401f3c0$0c05db40$@prosentient.com.au> Message-ID: I gave another try at multi-stage builds. It turns out you can tag the intermediate image by building them first with `docker build --target ...` so my problem with multi-stage builds is gone :) The result is an image of ~875MB. I pushed it on https://hub.docker.com/r/julianmaurice/koha with the tag master-slim Le 19/02/2020 à 01:17, dcook at prosentient.com.au a écrit : > Mmm that’s a good point. The smaller attack surface is something I harp > on about a lot when it comes to making minimal images. That’s actually > led me down some very fun rabbit holes about operating systems and Linux > in particular. > > For instance, here’s the Dockerfile for ubuntu:latest. It’s actually > quite minimal with the majority of the work being done by “ADD > ubuntu-bionic-core-cloudimg-amd64-root.tar.gz /”, which can be found at > https://partner-images.canonical.com/core/bionic/current/ubuntu-bionic-core-cloudimg-amd64-root.tar.gz. > When you open that up, it’s just a small Ubuntu root file system. Now > what does that get us? First I’ll backtrack. > > When the host boots, GRUB 2 finds the desired Linux kernel, loads the > kernel and the initramfs, and then transfers control to the kernel, > which runs the initramfs’s /init script (which typically invokes systemd > these days). That /init script finds the “real” root file system, mounts > it, and then executes systemd on the real root file system, which acts > as the init system and becomes our old faithful PID 1. > > Obviously that process doesn’t correspond to a container’s lifecycle. > When a container is started, the kernel is already running and the root > file system is already mounted. There’s already kernel mode and user > mode code running to manage the computer. Docker gives us isolation > using Linux kernel features like cgroups and namespaces, and takes care > of special file system cases like /dev, /proc/, and /sys for us. > > So a person doesn’t need a whole OS file system just to run a single > program in Docker. > > However, in our case, it gets complicated quickly, since Koha needs > MySQL client libraries, Zebra client libraries, and whatever other > libraries and files our Perl modules need (DateTime leverages OS-level > datetime files I think, there’s libxml, probably GD, etc.). If we were > really thorough, we probably could get Koha running in a very minimal > container, but it would take some work. It could be fun though. > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > Australia > > Office: 02 9212 0899 > > Direct: 02 8005 0595 > > *From:*Koha-devel *On > Behalf Of *Kyle Hall > *Sent:* Tuesday, 18 February 2020 10:43 PM > *To:* Julian Maurice > *Cc:* koha-devel > *Subject:* Re: [Koha-devel] Minimal docker images for Koha > > This is fantastic Julian! The only thing I can contribute that hasn't > already been said by you or David is to suggest taking a look at MiniDeb > as a base image ( https://github.com/bitnami/minideb ). I would also > suggest using quay.io to build and host your Docker > images, as it has built in security scanning. I prefer minimal install > images not for size reduction ( though it is nice ), but for the smaller > attack surface they provide. Fewer things installed means fewer exploits > available! > > Kyle > > --- > > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > Crawford County Federated Library System ( http://www.ccfls.org ) > > On Mon, Feb 17, 2020 at 12:59 PM Julian Maurice > > wrote: > > Hi all, > > I've been playing with docker lately, and I tried to build a minimal > docker image for Koha. Here are the results. > > My goals were: > * Install only required "things" to get Koha up and running, and > nothing > else (no testing or dev tools), > * No external dependencies except CPAN > * Follow Docker best practices as much as possible > > The resulting images are here: > https://hub.docker.com/repository/docker/julianmaurice/koha > > and the Dockerfiles are here: > https://github.com/jajm/koha-docker > > A few things worth mentioning: > > * I tried to build the smallest image possible by using alpine or perl > slim images at first but it was not that great, because the perl > version > shipped with those images is missing some libs, which cause > MARC::Charset to build a database of several hundreds MBs (which is > only > 5MBs with a standard perl version). So I chose a more standard image > (debian:buster) as base. > > * Koha doesn't work well when running with a perl version different > than > the system perl installed in /usr/bin/perl. For example, the > updatedatabase doesn't work when called from the web installer. This is > because Perl scripts are called directly as executable files, and > shebangs contain '/usr/bin/perl'. Same problem from > misc/translator/translate which calls tmpl_process3.pl > . > > * I tried to make the Koha installation as self-contained as possible. > Almost everything is installed as a non-root user in /home/koha, > including Perl dependencies. > > * It doesn't need a reverse proxy such as apache or nginx. The > necessary > URL rewriting is handled in PSGI file. The container expose two ports, > one for intranet, the other one for OPAC. > > * Each Perl dependency is installed in its latest version, so expect > things to break. I can only confirm that the webinstaller, basic > cataloguing and search/indexation work. I did not test anything else. > > * There are docker-compose.yml files in the github repository to get > Koha running quickly with mariadb, memcached and elasticsearch. > > * Zebra is not installed > > * Images weigh ~1.15GB uncompressed (koha sources included) > > If you made it this far, thanks for reading :) > And if you want to use these docker images, you should start by reading > https://github.com/jajm/koha-docker/blob/master/README.md > > -- > Julian Maurice > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -- Julian Maurice BibLibre From dcook at prosentient.com.au Fri Feb 21 01:22:28 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Fri, 21 Feb 2020 11:22:28 +1100 Subject: [Koha-devel] Minimal docker images for Koha In-Reply-To: References: <030f01d5e6ba$0401f3c0$0c05db40$@prosentient.com.au> Message-ID: <050401d5e84d$000e4a40$002adec0$@prosentient.com.au> Cool! Nice one, Julian! David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -----Original Message----- From: Julian Maurice Sent: Thursday, 20 February 2020 7:27 PM To: dcook at prosentient.com.au; 'Kyle Hall' Cc: 'koha-devel' Subject: Re: [Koha-devel] Minimal docker images for Koha I gave another try at multi-stage builds. It turns out you can tag the intermediate image by building them first with `docker build --target ...` so my problem with multi-stage builds is gone :) The result is an image of ~875MB. I pushed it on https://hub.docker.com/r/julianmaurice/koha with the tag master-slim Le 19/02/2020 à 01:17, dcook at prosentient.com.au a écrit : > Mmm that’s a good point. The smaller attack surface is something I > harp on about a lot when it comes to making minimal images. That’s > actually led me down some very fun rabbit holes about operating > systems and Linux in particular. > > For instance, here’s the Dockerfile for ubuntu:latest. It’s actually > quite minimal with the majority of the work being done by “ADD > ubuntu-bionic-core-cloudimg-amd64-root.tar.gz /”, which can be found > at https://partner-images.canonical.com/core/bionic/current/ubuntu-bionic-core-cloudimg-amd64-root.tar.gz. > When you open that up, it’s just a small Ubuntu root file system. Now > what does that get us? First I’ll backtrack. > > When the host boots, GRUB 2 finds the desired Linux kernel, loads the > kernel and the initramfs, and then transfers control to the kernel, > which runs the initramfs’s /init script (which typically invokes > systemd these days). That /init script finds the “real” root file > system, mounts it, and then executes systemd on the real root file > system, which acts as the init system and becomes our old faithful PID 1. > > Obviously that process doesn’t correspond to a container’s lifecycle. > When a container is started, the kernel is already running and the > root file system is already mounted. There’s already kernel mode and > user mode code running to manage the computer. Docker gives us > isolation using Linux kernel features like cgroups and namespaces, and > takes care of special file system cases like /dev, /proc/, and /sys for us. > > So a person doesn’t need a whole OS file system just to run a single > program in Docker. > > However, in our case, it gets complicated quickly, since Koha needs > MySQL client libraries, Zebra client libraries, and whatever other > libraries and files our Perl modules need (DateTime leverages OS-level > datetime files I think, there’s libxml, probably GD, etc.). If we were > really thorough, we probably could get Koha running in a very minimal > container, but it would take some work. It could be fun though. > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > Australia > > Office: 02 9212 0899 > > Direct: 02 8005 0595 > > *From:*Koha-devel *On > Behalf Of *Kyle Hall > *Sent:* Tuesday, 18 February 2020 10:43 PM > *To:* Julian Maurice > *Cc:* koha-devel > *Subject:* Re: [Koha-devel] Minimal docker images for Koha > > This is fantastic Julian! The only thing I can contribute that hasn't > already been said by you or David is to suggest taking a look at > MiniDeb as a base image ( https://github.com/bitnami/minideb ). I > would also suggest using quay.io to build and host > your Docker images, as it has built in security scanning. I prefer > minimal install images not for size reduction ( though it is nice ), > but for the smaller attack surface they provide. Fewer things > installed means fewer exploits available! > > Kyle > > --- > > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) Meadville Public > Library ( http://www.meadvillelibrary.org ) Crawford County Federated > Library System ( http://www.ccfls.org ) > > On Mon, Feb 17, 2020 at 12:59 PM Julian Maurice > > wrote: > > Hi all, > > I've been playing with docker lately, and I tried to build a minimal > docker image for Koha. Here are the results. > > My goals were: > * Install only required "things" to get Koha up and running, and > nothing > else (no testing or dev tools), > * No external dependencies except CPAN > * Follow Docker best practices as much as possible > > The resulting images are here: > https://hub.docker.com/repository/docker/julianmaurice/koha > > and the Dockerfiles are here: > https://github.com/jajm/koha-docker > > A few things worth mentioning: > > * I tried to build the smallest image possible by using alpine or perl > slim images at first but it was not that great, because the perl > version > shipped with those images is missing some libs, which cause > MARC::Charset to build a database of several hundreds MBs (which is > only > 5MBs with a standard perl version). So I chose a more standard image > (debian:buster) as base. > > * Koha doesn't work well when running with a perl version different > than > the system perl installed in /usr/bin/perl. For example, the > updatedatabase doesn't work when called from the web installer. This is > because Perl scripts are called directly as executable files, and > shebangs contain '/usr/bin/perl'. Same problem from > misc/translator/translate which calls tmpl_process3.pl > . > > * I tried to make the Koha installation as self-contained as possible. > Almost everything is installed as a non-root user in /home/koha, > including Perl dependencies. > > * It doesn't need a reverse proxy such as apache or nginx. The > necessary > URL rewriting is handled in PSGI file. The container expose two ports, > one for intranet, the other one for OPAC. > > * Each Perl dependency is installed in its latest version, so expect > things to break. I can only confirm that the webinstaller, basic > cataloguing and search/indexation work. I did not test anything else. > > * There are docker-compose.yml files in the github repository to get > Koha running quickly with mariadb, memcached and elasticsearch. > > * Zebra is not installed > > * Images weigh ~1.15GB uncompressed (koha sources included) > > If you made it this far, thanks for reading :) > And if you want to use these docker images, you should start by reading > https://github.com/jajm/koha-docker/blob/master/README.md > > -- > Julian Maurice > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -- Julian Maurice BibLibre -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From dcook at prosentient.com.au Fri Feb 21 01:30:07 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Fri, 21 Feb 2020 11:30:07 +1100 Subject: [Koha-devel] Minimal docker images for Koha In-Reply-To: <043c01d5e7a2$2e7efc90$8b7cf5b0$@prosentient.com.au> References: <9ed949eb-a716-589e-6b48-2b8daa2bd25f@biblibre.com> <032001d5e6ba$78a7dc30$69f79490$@prosentient.com.au> <043c01d5e7a2$2e7efc90$8b7cf5b0$@prosentient.com.au> Message-ID: <050b01d5e84e$118aa650$349ff2f0$@prosentient.com.au> Actually, now that I think about it, I assume an Apache-less Koha would also lose support for web-facing OPAC plugins (like the EBSCO EDS plugin)? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Koha-devel On Behalf Of dcook at prosentient.com.au Sent: Thursday, 20 February 2020 3:00 PM To: 'Kyle Hall' Cc: 'koha-devel' Subject: Re: [Koha-devel] Minimal docker images for Koha Exactly! I would love to see a task queue based record importer. (I keep thinking about a Koha plugin to provide a web ui for scheduling OAI-PMH harvesting, and then third-party applications that can consume from the task queue, stage the records… probably via the REST API… and then enqueue tasks to a high performance record importer worker…) Are you going to the Hackfest in Marseille? (I wanted to go this year but life is just too hectic this year, although planning to go to Kohacon in October.) A task queue could be a great Hackfest project… David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Kyle Hall > Sent: Thursday, 20 February 2020 12:04 AM To: David Cook > Cc: Julian Maurice >; koha-devel > Subject: Re: [Koha-devel] Minimal docker images for Koha Agreed! I think a task queue would be a huge benefit to Koha, we have so many long running batch operations. Kyle --- http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) On Tue, Feb 18, 2020 at 7:21 PM > wrote: Funny I was just looking at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15032. One of these days we should push forward more on queues: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -----Original Message----- From: Koha-devel > On Behalf Of Julian Maurice Sent: Tuesday, 18 February 2020 11:11 PM To: Kyle Hall > Cc: koha-devel > Subject: Re: [Koha-devel] Minimal docker images for Koha Are you talking about these files https://github.com/Koha-Community/Koha/blob/master/debian/templates/apache-shared-intranet-plack.conf#L14-L21 ? I did nothing specific, so they are probably broken :) Le 18/02/2020 à 12:45, Kyle Hall a écrit : > One other question, how does this handle scripts that Koha > specifically does not execute using plack? > > Kyle > > --- > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) Meadville Public > Library ( http://www.meadvillelibrary.org ) Crawford County Federated > Library System ( http://www.ccfls.org ) > > > On Tue, Feb 18, 2020 at 6:43 AM Kyle Hall > >> wrote: > > This is fantastic Julian! The only thing I can contribute that > hasn't already been said by you or David is to suggest taking a look > at MiniDeb as a base image ( https://github.com/bitnami/minideb ). I > would also suggest using quay.io to build and host > your Docker images, as it has built in security scanning. I prefer > minimal install images not for size reduction ( though it is nice ), > but for the smaller attack surface they provide. Fewer things > installed means fewer exploits available! > > Kyle > > --- > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > Crawford County Federated Library System ( http://www.ccfls.org ) > > > On Mon, Feb 17, 2020 at 12:59 PM Julian Maurice > >> > wrote: > > Hi all, > > I've been playing with docker lately, and I tried to build a > minimal > docker image for Koha. Here are the results. > > My goals were: > * Install only required "things" to get Koha up and running, and > nothing > else (no testing or dev tools), > * No external dependencies except CPAN > * Follow Docker best practices as much as possible > > The resulting images are here: > https://hub.docker.com/repository/docker/julianmaurice/koha > > and the Dockerfiles are here: > https://github.com/jajm/koha-docker > > A few things worth mentioning: > > * I tried to build the smallest image possible by using alpine > or perl > slim images at first but it was not that great, because the perl > version > shipped with those images is missing some libs, which cause > MARC::Charset to build a database of several hundreds MBs (which > is only > 5MBs with a standard perl version). So I chose a more standard > image > (debian:buster) as base. > > * Koha doesn't work well when running with a perl version > different than > the system perl installed in /usr/bin/perl. For example, the > updatedatabase doesn't work when called from the web installer. > This is > because Perl scripts are called directly as executable files, and > shebangs contain '/usr/bin/perl'. Same problem from > misc/translator/translate which calls tmpl_process3.pl > . > > * I tried to make the Koha installation as self-contained as > possible. > Almost everything is installed as a non-root user in /home/koha, > including Perl dependencies. > > * It doesn't need a reverse proxy such as apache or nginx. The > necessary > URL rewriting is handled in PSGI file. The container expose two > ports, > one for intranet, the other one for OPAC. > > * Each Perl dependency is installed in its latest version, so > expect > things to break. I can only confirm that the webinstaller, basic > cataloguing and search/indexation work. I did not test anything > else. > > * There are docker-compose.yml files in the github repository to > get > Koha running quickly with mariadb, memcached and elasticsearch. > > * Zebra is not installed > > * Images weigh ~1.15GB uncompressed (koha sources included) > > If you made it this far, thanks for reading :) > And if you want to use these docker images, you should start by > reading > https://github.com/jajm/koha-docker/blob/master/README.md > > -- > Julian Maurice > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -- Julian Maurice BibLibre _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From kyle.m.hall at gmail.com Fri Feb 21 13:27:27 2020 From: kyle.m.hall at gmail.com (Kyle Hall) Date: Fri, 21 Feb 2020 07:27:27 -0500 Subject: [Koha-devel] Minimal docker images for Koha In-Reply-To: <050b01d5e84e$118aa650$349ff2f0$@prosentient.com.au> References: <9ed949eb-a716-589e-6b48-2b8daa2bd25f@biblibre.com> <032001d5e6ba$78a7dc30$69f79490$@prosentient.com.au> <043c01d5e7a2$2e7efc90$8b7cf5b0$@prosentient.com.au> <050b01d5e84e$118aa650$349ff2f0$@prosentient.com.au> Message-ID: Plugin code is loaded into Plack processes. Does the EDS plugin contain cgi scripts that wouldn't run under plack? Getting all scripts to run under plack is definitely a goal we should have, but a short term kludge would be to run two containers, one plack and one cgi, and to direct traffic from a proxy to the correct container based on the url. Not elegant, but functional. --- http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) On Thu, Feb 20, 2020 at 7:30 PM wrote: > Actually, now that I think about it, I assume an Apache-less Koha would > also lose support for web-facing OPAC plugins (like the EBSCO EDS plugin)? > > > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > Australia > > > > Office: 02 9212 0899 > > Direct: 02 8005 0595 > > > > *From:* Koha-devel *On > Behalf Of *dcook at prosentient.com.au > *Sent:* Thursday, 20 February 2020 3:00 PM > *To:* 'Kyle Hall' > *Cc:* 'koha-devel' > *Subject:* Re: [Koha-devel] Minimal docker images for Koha > > > > Exactly! I would love to see a task queue based record importer. (I keep > thinking about a Koha plugin to provide a web ui for scheduling OAI-PMH > harvesting, and then third-party applications that can consume from the > task queue, stage the records… probably via the REST API… and then enqueue > tasks to a high performance record importer worker…) > > > > Are you going to the Hackfest in Marseille? (I wanted to go this year but > life is just too hectic this year, although planning to go to Kohacon in > October.) A task queue could be a great Hackfest project… > > > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > Australia > > > > Office: 02 9212 0899 > > Direct: 02 8005 0595 > > > > *From:* Kyle Hall > *Sent:* Thursday, 20 February 2020 12:04 AM > *To:* David Cook > *Cc:* Julian Maurice ; koha-devel < > koha-devel at lists.koha-community.org> > *Subject:* Re: [Koha-devel] Minimal docker images for Koha > > > > Agreed! I think a task queue would be a huge benefit to Koha, we have so > many long running batch operations. > > > > Kyle > > > > --- > > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > Crawford County Federated Library System ( http://www.ccfls.org ) > > > > > > On Tue, Feb 18, 2020 at 7:21 PM wrote: > > Funny I was just looking at > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15032. > > One of these days we should push forward more on queues: > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417. > > David Cook > Systems Librarian > Prosentient Systems > 72/330 Wattle St > Ultimo, NSW 2007 > Australia > > Office: 02 9212 0899 > Direct: 02 8005 0595 > > -----Original Message----- > From: Koha-devel On Behalf > Of Julian Maurice > Sent: Tuesday, 18 February 2020 11:11 PM > To: Kyle Hall > Cc: koha-devel > Subject: Re: [Koha-devel] Minimal docker images for Koha > > Are you talking about these files > > https://github.com/Koha-Community/Koha/blob/master/debian/templates/apache-shared-intranet-plack.conf#L14-L21 > ? > > I did nothing specific, so they are probably broken :) > > Le 18/02/2020 à 12:45, Kyle Hall a écrit : > > One other question, how does this handle scripts that Koha > > specifically does not execute using plack? > > > > Kyle > > > > --- > > http://www.kylehall.info > > ByWater Solutions ( http://bywatersolutions.com ) Meadville Public > > Library ( http://www.meadvillelibrary.org ) Crawford County Federated > > Library System ( http://www.ccfls.org ) > > > > > > On Tue, Feb 18, 2020 at 6:43 AM Kyle Hall > > wrote: > > > > This is fantastic Julian! The only thing I can contribute that > > hasn't already been said by you or David is to suggest taking a look > > at MiniDeb as a base image ( https://github.com/bitnami/minideb ). I > > would also suggest using quay.io to build and host > > your Docker images, as it has built in security scanning. I prefer > > minimal install images not for size reduction ( though it is nice ), > > but for the smaller attack surface they provide. Fewer things > > installed means fewer exploits available! > > > > Kyle > > > > --- > > http://www.kylehall.info > > ByWater Solutions ( http://bywatersolutions.com ) > > Meadville Public Library ( http://www.meadvillelibrary.org ) > > Crawford County Federated Library System ( http://www.ccfls.org ) > > > > > > On Mon, Feb 17, 2020 at 12:59 PM Julian Maurice > > > > > wrote: > > > > Hi all, > > > > I've been playing with docker lately, and I tried to build a > > minimal > > docker image for Koha. Here are the results. > > > > My goals were: > > * Install only required "things" to get Koha up and running, and > > nothing > > else (no testing or dev tools), > > * No external dependencies except CPAN > > * Follow Docker best practices as much as possible > > > > The resulting images are here: > > https://hub.docker.com/repository/docker/julianmaurice/koha > > > > and the Dockerfiles are here: > > https://github.com/jajm/koha-docker > > > > A few things worth mentioning: > > > > * I tried to build the smallest image possible by using alpine > > or perl > > slim images at first but it was not that great, because the perl > > version > > shipped with those images is missing some libs, which cause > > MARC::Charset to build a database of several hundreds MBs (which > > is only > > 5MBs with a standard perl version). So I chose a more standard > > image > > (debian:buster) as base. > > > > * Koha doesn't work well when running with a perl version > > different than > > the system perl installed in /usr/bin/perl. For example, the > > updatedatabase doesn't work when called from the web installer. > > This is > > because Perl scripts are called directly as executable files, and > > shebangs contain '/usr/bin/perl'. Same problem from > > misc/translator/translate which calls tmpl_process3.pl > > . > > > > * I tried to make the Koha installation as self-contained as > > possible. > > Almost everything is installed as a non-root user in /home/koha, > > including Perl dependencies. > > > > * It doesn't need a reverse proxy such as apache or nginx. The > > necessary > > URL rewriting is handled in PSGI file. The container expose two > > ports, > > one for intranet, the other one for OPAC. > > > > * Each Perl dependency is installed in its latest version, so > > expect > > things to break. I can only confirm that the webinstaller, basic > > cataloguing and search/indexation work. I did not test anything > > else. > > > > * There are docker-compose.yml files in the github repository to > > get > > Koha running quickly with mariadb, memcached and elasticsearch. > > > > * Zebra is not installed > > > > * Images weigh ~1.15GB uncompressed (koha sources included) > > > > If you made it this far, thanks for reading :) > > And if you want to use these docker images, you should start by > > reading > > https://github.com/jajm/koha-docker/blob/master/README.md > > > > -- > > Julian Maurice > > BibLibre > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at lists.koha-community.org > > > > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ > > git : http://git.koha-community.org/ > > bugs : http://bugs.koha-community.org/ > > > > -- > Julian Maurice > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ git : > http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Mon Feb 24 00:01:22 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Mon, 24 Feb 2020 10:01:22 +1100 Subject: [Koha-devel] Minimal docker images for Koha In-Reply-To: References: <9ed949eb-a716-589e-6b48-2b8daa2bd25f@biblibre.com> <032001d5e6ba$78a7dc30$69f79490$@prosentient.com.au> <043c01d5e7a2$2e7efc90$8b7cf5b0$@prosentient.com.au> <050b01d5e84e$118aa650$349ff2f0$@prosentient.com.au> Message-ID: <05e001d5ea9d$2ab7eec0$8027cc40$@prosentient.com.au> It could just be that I misunderstand how the plugins work with Plack, but when I use Koha via CGI, this is the path that is being used: /plugin/Koha/Plugin/EDS/opac/eds-search.pl?q=Search?query-1=AND,:{test}&default=1. I don’t think that would work using https://github.com/jajm/koha-docker/blob/master/master/app.psgi? I think just adding another mount would do the trick though? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Kyle Hall Sent: Friday, 21 February 2020 11:27 PM To: David Cook Cc: Julian Maurice ; koha-devel Subject: Re: [Koha-devel] Minimal docker images for Koha Plugin code is loaded into Plack processes. Does the EDS plugin contain cgi scripts that wouldn't run under plack? Getting all scripts to run under plack is definitely a goal we should have, but a short term kludge would be to run two containers, one plack and one cgi, and to direct traffic from a proxy to the correct container based on the url. Not elegant, but functional. --- http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) On Thu, Feb 20, 2020 at 7:30 PM > wrote: Actually, now that I think about it, I assume an Apache-less Koha would also lose support for web-facing OPAC plugins (like the EBSCO EDS plugin)? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Koha-devel > On Behalf Of dcook at prosentient.com.au Sent: Thursday, 20 February 2020 3:00 PM To: 'Kyle Hall' > Cc: 'koha-devel' > Subject: Re: [Koha-devel] Minimal docker images for Koha Exactly! I would love to see a task queue based record importer. (I keep thinking about a Koha plugin to provide a web ui for scheduling OAI-PMH harvesting, and then third-party applications that can consume from the task queue, stage the records… probably via the REST API… and then enqueue tasks to a high performance record importer worker…) Are you going to the Hackfest in Marseille? (I wanted to go this year but life is just too hectic this year, although planning to go to Kohacon in October.) A task queue could be a great Hackfest project… David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Kyle Hall > Sent: Thursday, 20 February 2020 12:04 AM To: David Cook > Cc: Julian Maurice >; koha-devel > Subject: Re: [Koha-devel] Minimal docker images for Koha Agreed! I think a task queue would be a huge benefit to Koha, we have so many long running batch operations. Kyle --- http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) On Tue, Feb 18, 2020 at 7:21 PM > wrote: Funny I was just looking at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15032. One of these days we should push forward more on queues: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -----Original Message----- From: Koha-devel > On Behalf Of Julian Maurice Sent: Tuesday, 18 February 2020 11:11 PM To: Kyle Hall > Cc: koha-devel > Subject: Re: [Koha-devel] Minimal docker images for Koha Are you talking about these files https://github.com/Koha-Community/Koha/blob/master/debian/templates/apache-shared-intranet-plack.conf#L14-L21 ? I did nothing specific, so they are probably broken :) Le 18/02/2020 à 12:45, Kyle Hall a écrit : > One other question, how does this handle scripts that Koha > specifically does not execute using plack? > > Kyle > > --- > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) Meadville Public > Library ( http://www.meadvillelibrary.org ) Crawford County Federated > Library System ( http://www.ccfls.org ) > > > On Tue, Feb 18, 2020 at 6:43 AM Kyle Hall > >> wrote: > > This is fantastic Julian! The only thing I can contribute that > hasn't already been said by you or David is to suggest taking a look > at MiniDeb as a base image ( https://github.com/bitnami/minideb ). I > would also suggest using quay.io to build and host > your Docker images, as it has built in security scanning. I prefer > minimal install images not for size reduction ( though it is nice ), > but for the smaller attack surface they provide. Fewer things > installed means fewer exploits available! > > Kyle > > --- > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > Crawford County Federated Library System ( http://www.ccfls.org ) > > > On Mon, Feb 17, 2020 at 12:59 PM Julian Maurice > >> > wrote: > > Hi all, > > I've been playing with docker lately, and I tried to build a > minimal > docker image for Koha. Here are the results. > > My goals were: > * Install only required "things" to get Koha up and running, and > nothing > else (no testing or dev tools), > * No external dependencies except CPAN > * Follow Docker best practices as much as possible > > The resulting images are here: > https://hub.docker.com/repository/docker/julianmaurice/koha > > and the Dockerfiles are here: > https://github.com/jajm/koha-docker > > A few things worth mentioning: > > * I tried to build the smallest image possible by using alpine > or perl > slim images at first but it was not that great, because the perl > version > shipped with those images is missing some libs, which cause > MARC::Charset to build a database of several hundreds MBs (which > is only > 5MBs with a standard perl version). So I chose a more standard > image > (debian:buster) as base. > > * Koha doesn't work well when running with a perl version > different than > the system perl installed in /usr/bin/perl. For example, the > updatedatabase doesn't work when called from the web installer. > This is > because Perl scripts are called directly as executable files, and > shebangs contain '/usr/bin/perl'. Same problem from > misc/translator/translate which calls tmpl_process3.pl > . > > * I tried to make the Koha installation as self-contained as > possible. > Almost everything is installed as a non-root user in /home/koha, > including Perl dependencies. > > * It doesn't need a reverse proxy such as apache or nginx. The > necessary > URL rewriting is handled in PSGI file. The container expose two > ports, > one for intranet, the other one for OPAC. > > * Each Perl dependency is installed in its latest version, so > expect > things to break. I can only confirm that the webinstaller, basic > cataloguing and search/indexation work. I did not test anything > else. > > * There are docker-compose.yml files in the github repository to > get > Koha running quickly with mariadb, memcached and elasticsearch. > > * Zebra is not installed > > * Images weigh ~1.15GB uncompressed (koha sources included) > > If you made it this far, thanks for reading :) > And if you want to use these docker images, you should start by > reading > https://github.com/jajm/koha-docker/blob/master/README.md > > -- > Julian Maurice > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -- Julian Maurice BibLibre _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From joy at bywatersolutions.com Tue Feb 25 00:31:04 2020 From: joy at bywatersolutions.com (Joy Nelson) Date: Mon, 24 Feb 2020 16:31:04 -0700 Subject: [Koha-devel] Koha 19.11.03 Release Message-ID: Greetings! The Koha community is proud to announce the release of Koha 19.11.03. This is a maintenance release containing 7 enhancements and 78 bugfixes The full release notes are available at https://koha-community.org/koha-19-11-03-release/ Debian packages will be updated within a few days Joy Nelson President, Koha Division ByWater Solutions Support and Consulting for Open Source Software Phone/Fax (888)900-8944 What is Koha? -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Tue Feb 25 07:48:35 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Tue, 25 Feb 2020 17:48:35 +1100 Subject: [Koha-devel] Problems when using multiple CGI objects in a CGI script Message-ID: <06bb01d5eba7$9a4dbf70$cee93e50$@prosentient.com.au> Hi all, Just thought I'd share an issue I encountered today. You can see the details at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24719, but it boils down to how using multiple CGI objects (using the CGI module) can lead to unexpected behaviour. In this case, file uploads were failing in /cgi-bin/koha/tools/stage-marc-import.pl because the CGI object created in a different function in the included C4::Auth was setting and clearing global variables behind the scenes just by calling CGI->new(). Just sharing this I suppose so that we're careful with our use of the CGI module? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From kyle.m.hall at gmail.com Tue Feb 25 12:03:15 2020 From: kyle.m.hall at gmail.com (Kyle Hall) Date: Tue, 25 Feb 2020 06:03:15 -0500 Subject: [Koha-devel] Minimal docker images for Koha In-Reply-To: <05e001d5ea9d$2ab7eec0$8027cc40$@prosentient.com.au> References: <9ed949eb-a716-589e-6b48-2b8daa2bd25f@biblibre.com> <032001d5e6ba$78a7dc30$69f79490$@prosentient.com.au> <043c01d5e7a2$2e7efc90$8b7cf5b0$@prosentient.com.au> <050b01d5e84e$118aa650$349ff2f0$@prosentient.com.au> <05e001d5ea9d$2ab7eec0$8027cc40$@prosentient.com.au> Message-ID: I could be mistaken as well. I was under the impression that Plack loaded the plugin code into itself when the plugin was first run. I'm basing this on the fact that it used to be that updating a plugin did not reflect the updated info in the plugins table in the admin section for plugins. That particular issue has been resolved. I suppose the easiest way to test would be to load a plugin into a plack enabled Koha instance, make a minor change to the plugin's perl code ( like a warn statement or something ) and see if the change shows itself without restarting plack. If it doesn't, then plugins are probably running under plack. --- http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) On Sun, Feb 23, 2020 at 6:01 PM wrote: > It could just be that I misunderstand how the plugins work with Plack, but > when I use Koha via CGI, this is the path that is being used: > /plugin/Koha/Plugin/EDS/opac/ > eds-search.pl?q=Search?query-1=AND,:{test}&default=1 > . I > don’t think that would work using > https://github.com/jajm/koha-docker/blob/master/master/app.psgi? I think > just adding another mount would do the trick though? > > > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > Australia > > > > Office: 02 9212 0899 > > Direct: 02 8005 0595 > > > > *From:* Kyle Hall > *Sent:* Friday, 21 February 2020 11:27 PM > *To:* David Cook > *Cc:* Julian Maurice ; koha-devel < > koha-devel at lists.koha-community.org> > *Subject:* Re: [Koha-devel] Minimal docker images for Koha > > > > Plugin code is loaded into Plack processes. Does the EDS plugin contain > cgi scripts that wouldn't run under plack? > > > > Getting all scripts to run under plack is definitely a goal we should > have, but a short term kludge would be to run two containers, one plack and > one cgi, and to direct traffic from a proxy to the correct container based > on the url. Not elegant, but functional. > > > > --- > > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > Crawford County Federated Library System ( http://www.ccfls.org ) > > > > > > On Thu, Feb 20, 2020 at 7:30 PM wrote: > > Actually, now that I think about it, I assume an Apache-less Koha would > also lose support for web-facing OPAC plugins (like the EBSCO EDS plugin)? > > > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > Australia > > > > Office: 02 9212 0899 > > Direct: 02 8005 0595 > > > > *From:* Koha-devel *On > Behalf Of *dcook at prosentient.com.au > *Sent:* Thursday, 20 February 2020 3:00 PM > *To:* 'Kyle Hall' > *Cc:* 'koha-devel' > *Subject:* Re: [Koha-devel] Minimal docker images for Koha > > > > Exactly! I would love to see a task queue based record importer. (I keep > thinking about a Koha plugin to provide a web ui for scheduling OAI-PMH > harvesting, and then third-party applications that can consume from the > task queue, stage the records… probably via the REST API… and then enqueue > tasks to a high performance record importer worker…) > > > > Are you going to the Hackfest in Marseille? (I wanted to go this year but > life is just too hectic this year, although planning to go to Kohacon in > October.) A task queue could be a great Hackfest project… > > > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > Australia > > > > Office: 02 9212 0899 > > Direct: 02 8005 0595 > > > > *From:* Kyle Hall > *Sent:* Thursday, 20 February 2020 12:04 AM > *To:* David Cook > *Cc:* Julian Maurice ; koha-devel < > koha-devel at lists.koha-community.org> > *Subject:* Re: [Koha-devel] Minimal docker images for Koha > > > > Agreed! I think a task queue would be a huge benefit to Koha, we have so > many long running batch operations. > > > > Kyle > > > > --- > > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > Crawford County Federated Library System ( http://www.ccfls.org ) > > > > > > On Tue, Feb 18, 2020 at 7:21 PM wrote: > > Funny I was just looking at > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15032. > > One of these days we should push forward more on queues: > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417. > > David Cook > Systems Librarian > Prosentient Systems > 72/330 Wattle St > Ultimo, NSW 2007 > Australia > > Office: 02 9212 0899 > Direct: 02 8005 0595 > > -----Original Message----- > From: Koha-devel On Behalf > Of Julian Maurice > Sent: Tuesday, 18 February 2020 11:11 PM > To: Kyle Hall > Cc: koha-devel > Subject: Re: [Koha-devel] Minimal docker images for Koha > > Are you talking about these files > > https://github.com/Koha-Community/Koha/blob/master/debian/templates/apache-shared-intranet-plack.conf#L14-L21 > ? > > I did nothing specific, so they are probably broken :) > > Le 18/02/2020 à 12:45, Kyle Hall a écrit : > > One other question, how does this handle scripts that Koha > > specifically does not execute using plack? > > > > Kyle > > > > --- > > http://www.kylehall.info > > ByWater Solutions ( http://bywatersolutions.com ) Meadville Public > > Library ( http://www.meadvillelibrary.org ) Crawford County Federated > > Library System ( http://www.ccfls.org ) > > > > > > On Tue, Feb 18, 2020 at 6:43 AM Kyle Hall > > wrote: > > > > This is fantastic Julian! The only thing I can contribute that > > hasn't already been said by you or David is to suggest taking a look > > at MiniDeb as a base image ( https://github.com/bitnami/minideb ). I > > would also suggest using quay.io to build and host > > your Docker images, as it has built in security scanning. I prefer > > minimal install images not for size reduction ( though it is nice ), > > but for the smaller attack surface they provide. Fewer things > > installed means fewer exploits available! > > > > Kyle > > > > --- > > http://www.kylehall.info > > ByWater Solutions ( http://bywatersolutions.com ) > > Meadville Public Library ( http://www.meadvillelibrary.org ) > > Crawford County Federated Library System ( http://www.ccfls.org ) > > > > > > On Mon, Feb 17, 2020 at 12:59 PM Julian Maurice > > > > > wrote: > > > > Hi all, > > > > I've been playing with docker lately, and I tried to build a > > minimal > > docker image for Koha. Here are the results. > > > > My goals were: > > * Install only required "things" to get Koha up and running, and > > nothing > > else (no testing or dev tools), > > * No external dependencies except CPAN > > * Follow Docker best practices as much as possible > > > > The resulting images are here: > > https://hub.docker.com/repository/docker/julianmaurice/koha > > > > and the Dockerfiles are here: > > https://github.com/jajm/koha-docker > > > > A few things worth mentioning: > > > > * I tried to build the smallest image possible by using alpine > > or perl > > slim images at first but it was not that great, because the perl > > version > > shipped with those images is missing some libs, which cause > > MARC::Charset to build a database of several hundreds MBs (which > > is only > > 5MBs with a standard perl version). So I chose a more standard > > image > > (debian:buster) as base. > > > > * Koha doesn't work well when running with a perl version > > different than > > the system perl installed in /usr/bin/perl. For example, the > > updatedatabase doesn't work when called from the web installer. > > This is > > because Perl scripts are called directly as executable files, and > > shebangs contain '/usr/bin/perl'. Same problem from > > misc/translator/translate which calls tmpl_process3.pl > > . > > > > * I tried to make the Koha installation as self-contained as > > possible. > > Almost everything is installed as a non-root user in /home/koha, > > including Perl dependencies. > > > > * It doesn't need a reverse proxy such as apache or nginx. The > > necessary > > URL rewriting is handled in PSGI file. The container expose two > > ports, > > one for intranet, the other one for OPAC. > > > > * Each Perl dependency is installed in its latest version, so > > expect > > things to break. I can only confirm that the webinstaller, basic > > cataloguing and search/indexation work. I did not test anything > > else. > > > > * There are docker-compose.yml files in the github repository to > > get > > Koha running quickly with mariadb, memcached and elasticsearch. > > > > * Zebra is not installed > > > > * Images weigh ~1.15GB uncompressed (koha sources included) > > > > If you made it this far, thanks for reading :) > > And if you want to use these docker images, you should start by > > reading > > https://github.com/jajm/koha-docker/blob/master/README.md > > > > -- > > Julian Maurice > > BibLibre > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at lists.koha-community.org > > > > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ > > git : http://git.koha-community.org/ > > bugs : http://bugs.koha-community.org/ > > > > -- > Julian Maurice > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ git : > http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Tue Feb 25 12:17:50 2020 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Tue, 25 Feb 2020 12:17:50 +0100 Subject: [Koha-devel] Give a try to RabbitMQ (background jobs rewrite) - POC! In-Reply-To: References: Message-ID: Hi, Quick update: a new version of this development has been published. See bug 22417 comment 30 for more info. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417#c30 Please test, read the code, and provide feedbacks :) Cheers, Jonathan Le mar. 26 févr. 2019 à 16:57, Jonathan Druart a écrit : > > Hi devs, > > I have submited a proof of concept (POC) on bug 22417 (Delegate > background jobs execution). > The idea would be to isolate our background jobs code (the one in the > .pl) into module then use RabbitMQ to process them. > > More stuffs on the bug! > > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417 > > Cheers, > Jonathan From joy at bywatersolutions.com Tue Feb 25 18:03:55 2020 From: joy at bywatersolutions.com (Joy Nelson) Date: Tue, 25 Feb 2020 10:03:55 -0700 Subject: [Koha-devel] Update to Koha 19.11.03 Release In-Reply-To: References: Message-ID: Hello all! A quick update on the recent maintenance releases. All maintenance releases (18.11.14, 19.05.08, 19.11.03) contain a security update related to XSLT. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23290 "This patchset refines the XSLT processing configuration such that we are more secure by disallowing the processing of external stylesheets by default and adding a configuration option to re-enable the functionality." Cheers -joy On Mon, Feb 24, 2020 at 4:31 PM Joy Nelson wrote: > Greetings! > > The Koha community is proud to announce the release of Koha 19.11.03. > > This is a maintenance release containing 7 enhancements and 78 bugfixes > > The full release notes are available at > https://koha-community.org/koha-19-11-03-release/ > > Debian packages will be updated within a few days > > > Joy Nelson > President, Koha Division > > ByWater Solutions > Support and Consulting for Open Source Software > Phone/Fax (888)900-8944 > What is Koha? > > > -- Joy Nelson President, Koha Division ByWater Solutions Support and Consulting for Open Source Software Phone/Fax (888)900-8944 What is Koha? -------------- next part -------------- An HTML attachment was scrubbed... URL: From mtj at kohaaloha.com Wed Feb 26 11:59:14 2020 From: mtj at kohaaloha.com (Mason James) Date: Wed, 26 Feb 2020 23:59:14 +1300 Subject: [Koha-devel] Update to Koha 19.11.03 Release In-Reply-To: References: Message-ID: hi Folks, the latest packages are available cheers, Mason On 26/02/20 6:03 am, Joy Nelson wrote: > Hello all!  A quick update on the recent maintenance releases. > > All maintenance releases (18.11.14, 19.05.08, 19.11.03) contain a security update related to XSLT. > > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23290 > "This patchset refines the XSLT processing configuration such that we are more secure by disallowing the processing of external stylesheets by default and adding a configuration option to re-enable the functionality." > > > Cheers > -joy > > > On Mon, Feb 24, 2020 at 4:31 PM Joy Nelson > wrote: > > Greetings! > > The Koha community is proud to announce the release of Koha 19.11.03. > > This is a maintenance release containing 7 enhancements and 78 bugfixes > > The full release notes are available at > https://koha-community.org/koha-19-11-03-release/ > > Debian packages will be updated within a few days > > > Joy Nelson > President, Koha Division > > ByWater Solutions > Support and Consulting for Open Source Software > Phone/Fax (888)900-8944 > What is Koha? > > > > > -- > Joy Nelson > President, Koha Division > > ByWater Solutions > Support and Consulting for Open Source Software > Phone/Fax (888)900-8944 > What is Koha? > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ From agustinmoyano at theke.io Wed Feb 26 23:11:34 2020 From: agustinmoyano at theke.io (Agustin Moyano) Date: Wed, 26 Feb 2020 19:11:34 -0300 Subject: [Koha-devel] Give a try to RabbitMQ (background jobs rewrite) - POC! In-Reply-To: References: Message-ID: Hi Jonathan, very interesting work.. I'll give it a try as soon as I can. El mar., 25 de febrero de 2020 08:18, Jonathan Druart < jonathan.druart at bugs.koha-community.org> escribió: > Hi, > > Quick update: a new version of this development has been published. > See bug 22417 comment 30 for more info. > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417#c30 > > Please test, read the code, and provide feedbacks :) > > Cheers, > Jonathan > > Le mar. 26 févr. 2019 à 16:57, Jonathan Druart > a écrit : > > > > Hi devs, > > > > I have submited a proof of concept (POC) on bug 22417 (Delegate > > background jobs execution). > > The idea would be to isolate our background jobs code (the one in the > > .pl) into module then use RabbitMQ to process them. > > > > More stuffs on the bug! > > > > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417 > > > > Cheers, > > Jonathan > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kohanews at gmail.com Thu Feb 27 18:10:49 2020 From: kohanews at gmail.com (kohanews) Date: Thu, 27 Feb 2020 09:10:49 -0800 Subject: [Koha-devel] Koha Community Newsletter: February 2020 Message-ID: <3f073f6c-7bd4-7dd9-1911-379147305dd9@gmail.com> The Koha Community Newsletter for February 2020 is here: https://koha-community.org/koha-community-newsletter-february-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