Rebuild on each iviewer release, etc.

[joshmoore]

see: https://github.com/ome/omero-web-docker/blob/ea5babeda9bdf7b41e637e7f51391a5a55c992ff/standalone/Dockerfile

Every time there's a new release of one of the installed packages beyond omero-web we also need to re-release omero-web-docker. It would be ideal if this could be automated via GitHub actions.

[manics]

Could add a requirements.txt file with pinned versions, then let dependabot take care of it?

[sbesson]

Could add a requirements.txt file with pinned versions, then let dependabot take care of it?

Sounds like a very promising approach. I just tested the gitsubmodule capabilities of dependabotand am feeling very enthusiastic. I was searching for more details about the pip package-ecosystem - https://docs.github.com/en/github/administering-a-repository/configuration-options-for-dependency-updates#package-ecosystem - is it acting on requirements.txt, setup.py and/or Piplock files?

[manics]

For Python AFAIK it checks *.txt

[jburel]

cf. discussion on #63 case for extracting omero-web-standalone from this repo