OMERO.server CLI Plugin
Introduction
OMERO.py provides a plugin infrastructure for CLI tools. Most tools are intended for the general user wanting to login to a running OMERO.server. Other plugins like this one are intended for the management of the installation itself.
Dependencies
Direct dependencies of this plugin are:
Installation
See: OMERO documentation
Usage
See: OMERO documentation
Contributing
See: OMERO documentation
Developer installation
omero-server `depends on OMERO.py. If you want a developer installation of OMERO.py, replace ``pip install omero-py` with instructions at https://github.com/ome/omero-py.
For a development installation we recommend creating a virtualenv with the following setup (example assumes python3.6 but you can create and activate the virtualenv using any compatible Python):
python3.6 -mvenv venv . venv/bin/activate pip install zeroc-ice==3.6.5 pip install omero-py # OR dev install (see above) git clone https://github.com/ome/omero-cli-server cd omero-server pip install -e .
This will install the server plugins into your virtualenv as an editable package, so any edits to source files should be reflected in your installation.
Note some tests may not run when this module and/or omero-py are installed in editable mode.
Running tests
Unit tests are located under the test directory and can be run with pytest.
Integration tests
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.
Release process
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 [major|minor|patch]
specifying major, minor or patch depending on whether the development branch will be a major, minor or patch release. This will also add the .dev0 suffix.
Remember to git push all commits and tags.
License
omero-cli-server is released under the GPL.
Copyright
2020-2022, The Open Microscopy Environment
Metadata
Release files for omero-server 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| omero-server-0.4.0.tar.gz | 10.2 kB | Without provenance | Details for omero-server-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| omero_server-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for omero_server-0.4.0-py3-none-any.whl |
Total release size: 20.4 kB
Release files / omero-server-0.4.0.tar.gz
| Download URL | omero-server-0.4.0.tar.gz |
|---|---|
| Size | 10.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3bc7fcaf884b3b4b82076ad47f86d8e729f81ca6df8ad29634130fb50892b423
|
|
BLAKE2b-256 checksum How to use checksums |
66f38165247a0acc3abdb31da96b295f0285ba86f21cedd9581e4b57f2bbd153
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.18
|
Release files / omero_server-0.4.0-py3-none-any.whl
| Download URL | omero_server-0.4.0-py3-none-any.whl |
|---|---|
| Size | 10.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ddac3094e835f5ac5c2fa17049a24d2a9844e0f5dcefd922ec5b474004ed319d
|
|
BLAKE2b-256 checksum How to use checksums |
909f25184129b696332dc62d9ed90ee6f0179c52b571797c3a8a6aa4f99aa89d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.18
|
Security for omero-server 0.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.