I mean, files may be served directly from the web server and cached by varnish.. web server and plack could have a shared volume for static assets El lun., 2 de marzo de 2020 22:03, Agustin Moyano <agustinmoyano@theke.io> escribió:
I believe in that case if you use a shared volume between containers, plack won't be needed
El lun., 2 de marzo de 2020 20:21, <dcook@prosentient.com.au> escribió:
Could you speak more to that one, Kyle?
I was thinking the other day how Varnish could be used to cache responses for static assets, but that would still put load on the Plack server for the initial requests. Maybe not enough to be significant though. Would be interesting to experiment.
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 <kyle.m.hall@gmail.com> *Sent:* Tuesday, 3 March 2020 1:24 AM *To:* David Cook <dcook@prosentient.com.au> *Cc:* Julian Maurice <julian.maurice@biblibre.com>; Agustin Moyano < agustinmoyano@theke.io>; Koha Devel <Koha-devel@lists.koha-community.org> *Subject:* Re: [Koha-devel] Minimal docker images for Koha
For static assets, you could put something like Varnish in between as well.
---
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, Mar 1, 2020 at 9:45 PM <dcook@prosentient.com.au> wrote:
I'd also note that in production you'd probably want to use a reverse proxy in the same container as Starman for performance reasons, since the reverse proxy will do better than Starman at serving static assets. On a different Perl project, I've used HTTP::Server::PSGI for development, and it does well with the Perl, but really struggles to provide the static assets. (I suppose you could run a reverse proxy in a different container and share files using a mounted volume but I think you'd start getting headaches if you tried to scale that out at all.)
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 <koha-devel-bounces@lists.koha-community.org> On Behalf Of Julian Maurice Sent: Sunday, 1 March 2020 10:12 PM To: Agustin Moyano <agustinmoyano@theke.io>; Koha Devel < Koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] Minimal docker images for Koha
I believe that the problems we have with Debian buster are mostly related to the versions of Perl modules shipped with debian packages. Since these Dockerfiles install all Perl modules from CPAN in their latest version, I think you will have the same problems with an older version of Debian.
URL rewrite in PSGI file is handy for development, but that shouldn't be used in production. Indeed, a reverse proxy is still required in production environments.
Please note that images produced by these Dockerfiles are not intended to be used in production. As I said in my first message, you should expect things to break ;)
Le 01/03/2020 à 05:19, Agustin Moyano a écrit :
Sorry.. seems I send it only to Julian.. here goes again
El sáb., 29 de febrero de 2020 19:15, Agustin Moyano <agustinmoyano@theke.io <mailto:agustinmoyano@theke.io>> escribió:
Hi Julian, great work!!
I've also been working (interruptedly) for a couple of months on a docker version of Koha.
I focused on having as soon as possible a fully functional docker version of Koha, and didn't worry too much about doing things the docker way.. It's comforting to know you weren't tempted by de dark side of the force!
I thought of having first a production ready docker much like koha-testing-docker, and later split services into different containers. That's why I really, really loved your implementation of plack.psgi. URL rewrite in psgi brings independence day from Apache much closer! \o/.
Just some thoughts:
* Should you base your image on Debian buster? on https://wiki.koha-community.org/wiki/Koha_on_Debian says "Note: Debian 10 (Buster) is currently not recommended or supported, work is in progress to rectify this situation." * Even if there's no need for reverse proxy, I wouldn't discard having one on a separate container.. web servers like apache or nginx deal much better with attacks than exposing the service on it's own (First hand experience with a Java/Tomcat service I made once)
(https://security.stackexchange.com/questions/209111/security-benefits -of-reverse-proxying-java-tomcat-webapps-locally)
But overall, great job!
PS: If you'd like to take a peek of what I've done, here's the repo: https://gitlab.com/thekesolutions/koha-docker
-- Julian Maurice BibLibre _______________________________________________ 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/
_______________________________________________ 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/