jean-marie burel
jean-marie burel
The workflow is as follows: * ``omero/autogen_docs`` is run * one step in the script does the following ``omero/autogen_db_version.py $WORKSPACE/OMERO.server > omero/conf_autogen.py`` * ``conf_autogen.py`` is then used in ``conf.py`` to...
partially. The DB version will be the one that could have been modified but no change this time in DB version. The rest is hard-coded We will need something like...
I remember now having to add ``` print('version_omero_server = "5.6.5"') print('version_bioformats = "6.10.0"') print('version_blitz = "5.5.12"') print('version_server = "5.6.4"') print('version_romio = "5.7.0"') print('version_renderer = "5.5.10"') print('version_common = "5.6.7"') print('version_model =...
Option to update the dependencies as part of the scheduled daily build See https://github.com/ome/omero-documentation/pull/2258
@will-moore Does the recent work for ``omero-figure`` (cf. https://github.com/ome/omero-figure/pull/469) a good compromise we could promote?
We could add a Dockerfile to our repos and improve the doc. I will look into it.
* Guides have been "omero" focus even if we only use public data (mostly from IDR) for the examples, agree that a rename is necessary. * guide has info about...
Initial discussion about renaming https://github.com/ome/omero-guides/issues/5
* Section to "upload to S3" could be added to the guide under "upload/import"
As it stands you are right they are not the same, this is more after renaming/breaking up sections