[ome-users] omero Installation without nginx
Andreas Mueller
Andreas.Mueller at Biologie.Uni-Osnabrueck.DE
Thu Jan 24 12:51:45 GMT 2019
Hi Simon,
of course:
$ cd OMERO.server/
$ find . -type f | xargs grep -l '/3rdparty.pan.*ima'
brought me:
./lib/python/omeroweb/webgateway/static/webgateway/js/ome.viewportImage.js
./lib/python/omeroweb/static/webgateway/js/ome.viewportImage.js
./lib/python/omeroweb/static/omeroweb.viewer.min.js
and, as mentioned in trello, I've done:
$ sed -i "s/\/3rdparty\//3rdparty\//g"
for the three files. Restart web and ready.
____
I'll share my whitenoise experience
with best regards
Andreas
PS: How do you solve the port-80-problem in docker ?
On 24.01.19 11:29, Simon Li wrote:
> Hi Andreas
>
> All our production OMERO instances currently use Nginx, we haven't
> done any performance testing with Whitenoise. However based on the
> Whitenoise documentation I'd expect it to be fine for a small number
> of users. If you go into production with this setup it'd be great if
> you could follow up on this thread with your results, good or bad, as
> it's something others might be interested in.
>
> Could you point me to the lines in ome.viewportImage.js and
> omeroweb.viewer.min.js that you had to change? We've had a similar bug
> report before:
> https://trello.com/c/emmH0lCd/520-omeroweb-extraneous-forward-slash-for-static-asset-location.
>
> Thanks!
> Simon
>
> On Thu, 24 Jan 2019 at 10:33, Andreas Mueller wrote:
> Hi Simon,
>
> thanks for your mail!
>
> Ok, got that: I switched debug to "FALSE".
>
> I've installed "whitenoise". That was an easy task:
>
> pip install .. and
> config append ..
>
> - ready.
>
> And I don't have to worry about a nginx installation. Nice!
>
> >> Do I run in trouble later if I bring that in production ??
>
> a nice day for all
> Andreas
>
> PS: 2 notes:
>
> - the user omero can not start a service on port 80. I fixed that with
> a local port-forwarding. It's mutch cheaper than a running nginx!
>
> - whitenoise has troubles with double slashes in a URL '//'. Some
> icon's where broken.
>
> I fixed that by hardcoding the two files ome.viewportImage.js and
> the file omeroweb.viewer.min.js
>
> .. I hope that is enought. Hints are welcome :-)
>
>
>
> On 22.01.19 10:31, Simon Li wrote:
> > Hi Andreas
> >
> > You shouldn't run OMERO.web in in production with DEBUG enabled, see
> > the Django docs for an explanation:
> > https://docs.djangoproject.com/en/1.8/ref/settings/#debug
> >
> > It's possible to run OMERO.web without a web server using the
> > whitenoise package: http://whitenoise.evans.io/en/stable/ with this
> > OMERO.web configuration line:
> >
> > config append -- omero.web.middleware '{"index": 0, "class":
> > "whitenoise.middleware.WhiteNoiseMiddleware"}'
> >
> > For example this is used in one of our OMERO.web docker images for
> > convenience:
> > https://github.com/openmicroscopy/omero-web-docker/blob/5.4.9/standalone/Dockerfile
> >
> > Simon
> >
> >
> > Hi all,
> >
> > I've made my next Omero-Test-Installation without the nginx-part.
> >
> > It runs find (when, and only when I set the debug flag (?)) .. !
> >
> >
> > Are there still reasens to install the nginx cache webserver?
> >
> > Can I bring my installation in production-mode without disadvantages?
> >
> >
> > thanks a lot and have a nice day
> > Andreas
> >
> _______________________________________________
> ome-users mailing list
> ome-users at lists.openmicroscopy.org.uk
> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users
More information about the ome-users
mailing list