<div dir="ltr"><div>For static assets, you could put something like Varnish in between as well.</div><div><br></div><div><div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><div style="font-size:small">---<br></div></div><div><a href="http://www.kylehall.info" target="_blank">http://www.kylehall.info</a><br>ByWater Solutions ( <a href="http://bywatersolutions.com" target="_blank">http://bywatersolutions.com</a> )<br>Meadville Public Library ( <a href="http://www.meadvillelibrary.org" target="_blank">http://www.meadvillelibrary.org</a> )<br>Crawford County Federated Library System ( <a href="http://www.ccfls.org" target="_blank">http://www.ccfls.org</a> )<br></div></div></div></div></div></div></div></div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Mar 1, 2020 at 9:45 PM <<a href="mailto:dcook@prosentient.com.au">dcook@prosentient.com.au</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">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.)<br>
<br>
David Cook<br>
Systems Librarian<br>
Prosentient Systems<br>
72/330 Wattle St<br>
Ultimo, NSW 2007<br>
Australia<br>
<br>
Office: 02 9212 0899<br>
Direct: 02 8005 0595<br>
<br>
-----Original Message-----<br>
From: Koha-devel <<a href="mailto:koha-devel-bounces@lists.koha-community.org" target="_blank">koha-devel-bounces@lists.koha-community.org</a>> On Behalf Of Julian Maurice<br>
Sent: Sunday, 1 March 2020 10:12 PM<br>
To: Agustin Moyano <<a href="mailto:agustinmoyano@theke.io" target="_blank">agustinmoyano@theke.io</a>>; Koha Devel <<a href="mailto:Koha-devel@lists.koha-community.org" target="_blank">Koha-devel@lists.koha-community.org</a>><br>
Subject: Re: [Koha-devel] Minimal docker images for Koha<br>
<br>
I believe that the problems we have with Debian buster are mostly related to the versions of Perl modules shipped with debian packages. <br>
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.<br>
<br>
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.<br>
<br>
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 ;)<br>
<br>
Le 01/03/2020 à 05:19, Agustin Moyano a écrit :<br>
> Sorry.. seems I send it only to Julian.. here goes again<br>
> <br>
> El sáb., 29 de febrero de 2020 19:15, Agustin Moyano <br>
> <<a href="mailto:agustinmoyano@theke.io" target="_blank">agustinmoyano@theke.io</a> <mailto:<a href="mailto:agustinmoyano@theke.io" target="_blank">agustinmoyano@theke.io</a>>> escribió:<br>
> <br>
> Hi Julian, great work!!<br>
> <br>
> I've also been working (interruptedly) for a couple of months on a<br>
> docker version of Koha.<br>
> <br>
> I focused on having as soon as possible a fully functional docker<br>
> version of Koha, and didn't worry too much about doing things the<br>
> docker way.. It's comforting to know you weren't tempted by de dark<br>
> side of the force!<br>
> <br>
> I thought of having first a production ready docker much like<br>
> koha-testing-docker, and later split services into different<br>
> containers. That's why I really, really loved your implementation of<br>
> plack.psgi. URL rewrite in psgi brings independence day from Apache<br>
> much closer! \o/.<br>
> <br>
> Just some thoughts:<br>
> <br>
> * Should you base your image on Debian buster? on<br>
> <a href="https://wiki.koha-community.org/wiki/Koha_on_Debian" rel="noreferrer" target="_blank">https://wiki.koha-community.org/wiki/Koha_on_Debian</a> says "Note:<br>
> Debian 10 (Buster) is currently not recommended or supported,<br>
> work is in progress to rectify this situation."<br>
> * Even if there's no need for reverse proxy, I wouldn't discard<br>
> having one on a separate container.. web servers like apache or<br>
> nginx deal much better with attacks than exposing the service on<br>
> it's own (First hand experience with a Java/Tomcat service I<br>
> made once)<br>
> <br>
> (<a href="https://security.stackexchange.com/questions/209111/security-benefits" rel="noreferrer" target="_blank">https://security.stackexchange.com/questions/209111/security-benefits</a><br>
> -of-reverse-proxying-java-tomcat-webapps-locally)<br>
> <br>
> But overall, great job!<br>
> <br>
> PS: If you'd like to take a peek of what I've done, here's the repo:<br>
> <a href="https://gitlab.com/thekesolutions/koha-docker" rel="noreferrer" target="_blank">https://gitlab.com/thekesolutions/koha-docker</a><br>
> <br>
<br>
--<br>
Julian Maurice<br>
BibLibre<br>
_______________________________________________<br>
Koha-devel mailing list<br>
<a href="mailto:Koha-devel@lists.koha-community.org" target="_blank">Koha-devel@lists.koha-community.org</a><br>
<a href="https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" rel="noreferrer" target="_blank">https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br>
website : <a href="http://www.koha-community.org/" rel="noreferrer" target="_blank">http://www.koha-community.org/</a> git : <a href="http://git.koha-community.org/" rel="noreferrer" target="_blank">http://git.koha-community.org/</a> bugs : <a href="http://bugs.koha-community.org/" rel="noreferrer" target="_blank">http://bugs.koha-community.org/</a><br>
<br>
_______________________________________________<br>
Koha-devel mailing list<br>
<a href="mailto:Koha-devel@lists.koha-community.org" target="_blank">Koha-devel@lists.koha-community.org</a><br>
<a href="https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" rel="noreferrer" target="_blank">https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br>
website : <a href="http://www.koha-community.org/" rel="noreferrer" target="_blank">http://www.koha-community.org/</a><br>
git : <a href="http://git.koha-community.org/" rel="noreferrer" target="_blank">http://git.koha-community.org/</a><br>
bugs : <a href="http://bugs.koha-community.org/" rel="noreferrer" target="_blank">http://bugs.koha-community.org/</a><br>
</blockquote></div>