OMERO.web provides a web based client and plugin infrastructure.
Direct dependencies of OMERO.web are:
A WSGI capable web server
We recommend installing omero-web in a Python virtual environment. Here we show the install using Conda. For more details and other options, please see OMERO.py.
conda create -n myenv -c ome python=3.6 zeroc-ice36-python omero-py conda activate myenv pip install omero-web
Setting of the environment variable OMERODIR is required. $OMERODIR/var/log/ directory will contain log files. $OMERODIR/etc/grid/config.xml is used to store config:
For running omero-web in production with nginx, see See: OMERO.web install documentation. To run in development mode, see below.
See: OMERO documentation
For a development installation we recommend creating a virtual environment as described above. Then install OMERO.web into your virtual environment as an editable package, so that any edits to source files will be reflected in your installation.
git clone https://github.com/ome/omero-web cd omero-web pip install -e .
Note some omero-web tests may not run when this module and/or omero-py are installed in editable mode.
Configuration for developer usage:
omero config set omero.web.debug True omero config set omero.web.application_server development # If you want to connect to OMERO.server other than 'localhost' omero config append omero.web.server_list '["demo.openmicroscopy.org", 4064, "demo"]'
Then run omero-web in the foreground with:
omero web start ... Starting development server at http://127.0.0.1:4080/
Or, run Django directly:
cd omero-web python omeroweb/manage.py runserver 4080 ... Starting development server at http://127.0.0.1:4080/
The release of OMERO.web 5.14.0 requires an update of Django to 3.2.x. Plugin developers should read the Guide detailing how to migrate their plugin(s) to Django 3.2.x.
Unit tests are located under the test directory and can be run with pytest.
Integration tests are stored in the main repository (ome/openmicroscopy) and depend on the OMERO integration testing framework. Reading about Running and writing tests in the OMERO documentation is essential.
This repository uses bump2version to manage version numbers. To tag a release run:
$ bumpversion release
This will remove the .dev0 suffix from the current version, commit, and tag the release.
To switch back to a development version run:
$ bumpversion --no-tag patch
NB: this assumes next release will be a patch (see below). To complete the release, push the master branch and the release tag to origin:
$ git push origin master v5.8.0
If any PRs are merged that would require the next release to be a major or minor version (see semver.org) then that PR can include a version bump created via:
$ bumpversion --no-tag minor|major
If this hasn’t been performed prior to release and you wish to specify the next version number directly when creating the release, this can be achieved with:
$ bumpversion --new-version 5.9.0 release
Following omero-web release, need to update and release omero-web-docker.
OMERO.web is released under the AGPL.
2009-2022, The Open Microscopy Environment, Glencoe Software, Inc.
Release history Release notifications | RSS feed
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Hashes for omero_web-5.14.0-py3-none-any.whl