<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div dir="ltr">
<div>Thanks Andreas!</div>
<div><br>
</div>
<div>OMERO runs as an unprivileged user so can't bind to ports below 1024, but you should be able to use Docker port-forwarding to expose it as port 80. Something like:<br>
</div>
<div><br>
</div>
<div>docker run -p 80:4080 omero-docker</div>
<div><br>
</div>
<div>Should forward port 4080 inside the docker container to port 80 on your Docker host.</div>
<div><br>
</div>
<div>Hope this helps, Simon<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, 24 Jan 2019 at 12:51, Andreas Mueller <<a href="mailto:Andreas.Mueller@biologie.uni-osnabrueck.de">Andreas.Mueller@biologie.uni-osnabrueck.de</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">
Hi Simon,<br>
<br>
of course:<br>
<br>
$ cd OMERO.server/<br>
$ find . -type f | xargs grep -l '/3rdparty.pan.*ima'<br>
<br>
brought me:<br>
<br>
./lib/python/omeroweb/webgateway/static/webgateway/js/ome.viewportImage.js<br>
./lib/python/omeroweb/static/webgateway/js/ome.viewportImage.js<br>
./lib/python/omeroweb/static/omeroweb.viewer.min.js<br>
<br>
and, as mentioned in trello, I've done:<br>
<br>
$ sed -i "s/\/3rdparty\//3rdparty\//g" <br>
<br>
for the three files. Restart web and ready.<br>
____<br>
<br>
I'll share my whitenoise experience<br>
<br>
with best regards<br>
Andreas<br>
<br>
<br>
PS: How do you solve the port-80-problem in docker ?<br>
<br>
<br>
<br>
<br>
On 24.01.19 11:29, Simon Li wrote:<br>
> Hi Andreas<br>
> <br>
> All our production OMERO instances currently use Nginx, we haven't<br>
> done any performance testing with Whitenoise. However based on the<br>
> Whitenoise documentation I'd expect it to be fine for a small number<br>
> of users. If you go into production with this setup it'd be great if<br>
> you could follow up on this thread with your results, good or bad, as<br>
> it's something others might be interested in.<br>
> <br>
> Could you point me to the lines in ome.viewportImage.js and<br>
> omeroweb.viewer.min.js that you had to change? We've had a similar bug<br>
> report before:<br>
> <a href="https://trello.com/c/emmH0lCd/520-omeroweb-extraneous-forward-slash-for-static-asset-location" rel="noreferrer" target="_blank">
https://trello.com/c/emmH0lCd/520-omeroweb-extraneous-forward-slash-for-static-asset-location</a>.<br>
> <br>
> Thanks!<br>
> Simon<br>
> <br>
> On Thu, 24 Jan 2019 at 10:33, Andreas Mueller wrote:<br>
> Hi Simon,<br>
> <br>
> thanks for your mail!<br>
> <br>
> Ok, got that: I switched debug to "FALSE".<br>
> <br>
> I've installed "whitenoise". That was an easy task:<br>
> <br>
> pip install .. and<br>
> config append ..<br>
> <br>
> - ready.<br>
> <br>
> And I don't have to worry about a nginx installation. Nice!<br>
> <br>
> >> Do I run in trouble later if I bring that in production ??<br>
> <br>
> a nice day for all<br>
> Andreas<br>
> <br>
> PS: 2 notes:<br>
> <br>
> - the user omero can not start a service on port 80. I fixed that with<br>
> a local port-forwarding. It's mutch cheaper than a running nginx!<br>
> <br>
> - whitenoise has troubles with double slashes in a URL '//'. Some<br>
> icon's where broken.<br>
> <br>
> I fixed that by hardcoding the two files ome.viewportImage.js and<br>
> the file omeroweb.viewer.min.js<br>
> <br>
> .. I hope that is enought. Hints are welcome :-)<br>
> <br>
> <br>
> <br>
> On 22.01.19 10:31, Simon Li wrote:<br>
> > Hi Andreas<br>
> ><br>
> > You shouldn't run OMERO.web in in production with DEBUG enabled, see<br>
> > the Django docs for an explanation:<br>
> > <a href="https://docs.djangoproject.com/en/1.8/ref/settings/#debug" rel="noreferrer" target="_blank">
https://docs.djangoproject.com/en/1.8/ref/settings/#debug</a><br>
> ><br>
> > It's possible to run OMERO.web without a web server using the<br>
> > whitenoise package: <a href="http://whitenoise.evans.io/en/stable/" rel="noreferrer" target="_blank">
http://whitenoise.evans.io/en/stable/</a> with this<br>
> > OMERO.web configuration line:<br>
> ><br>
> > config append -- omero.web.middleware '{"index": 0, "class":<br>
> > "whitenoise.middleware.WhiteNoiseMiddleware"}'<br>
> ><br>
> > For example this is used in one of our OMERO.web docker images for<br>
> > convenience:<br>
> > <a href="https://github.com/openmicroscopy/omero-web-docker/blob/5.4.9/standalone/Dockerfile" rel="noreferrer" target="_blank">
https://github.com/openmicroscopy/omero-web-docker/blob/5.4.9/standalone/Dockerfile</a><br>
> ><br>
> > Simon<br>
> ><br>
> ><br>
> > Hi all,<br>
> ><br>
> > I've made my next Omero-Test-Installation without the nginx-part.<br>
> ><br>
> > It runs find (when, and only when I set the debug flag (?)) .. !<br>
> ><br>
> ><br>
> > Are there still reasens to install the nginx cache webserver?<br>
> ><br>
> > Can I bring my installation in production-mode without disadvantages?<br>
> ><br>
> ><br>
> > thanks a lot and have a nice day<br>
> > Andreas<br>
> ><br>
<br>
> _______________________________________________<br>
> ome-users mailing list<br>
> <a href="mailto:ome-users@lists.openmicroscopy.org.uk" target="_blank">ome-users@lists.openmicroscopy.org.uk</a><br>
> <a href="http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users" rel="noreferrer" target="_blank">
http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users</a><br>
<br>
_______________________________________________<br>
ome-users mailing list<br>
<a href="mailto:ome-users@lists.openmicroscopy.org.uk" target="_blank">ome-users@lists.openmicroscopy.org.uk</a><br>
<a href="http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users" rel="noreferrer" target="_blank">http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users</a><br>
</blockquote>
</div>
<br>
<span style="font-size:10pt;">The University of Dundee is a registered Scottish Charity, No: SC015096</span>
</body>
</html>