"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 <julian.maur...@biblibre.com> Sent: Tuesday, 18 February 2020 6:29 PM To: dc...@prosentient.com.au Cc: 'koha-devel' <koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] Minimal docker images for Koha Le Tue, 18 Feb 2020 17:29:42 +1100, <dc...@prosentient.com.au> 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.
signature.asc
Description: PGP signature
_______________________________________________ Koha-devel mailing list Koha-devel@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/
