Conversation
|
Downloaded Figure PDF of auto-imported fake: cc: @pwalczysko |
|
Conflicting PR. Removed from build DOCKER-merge#667. See the console output for more details.
--conflicts |
|
Indirectly tested some of these changes via https://doi.org/10.5281/zenodo.2593260. From my side, the auto-import feature was extremely useful and should be included in the Docker image. Given the deployment architecture, my only local addition was to use Happy to see this functionality extracted to a dedicated PR and sign off on it. |
|
Conflicting PR. Removed from build DOCKER-merge#711. See the console output for more details.
--conflicts |
|
Conflicting PR. Removed from build DOCKER-merge#712. See the console output for more details.
--conflicts |
|
Conflicting PR. Removed from build DOCKER-merge#713. See the console output for more details.
--conflicts |
|
We could follow the pattern of the omero-web-docker image where the base image is fairly empty and is designed to be extended, for instance as in the standalone image. This would also be a chance to add either a default public user account, or more generic functionality for creating default users, as started in #2 |
|
Conflicting PR. Removed from build DOCKER-merge#714. See the console output for more details.
--conflicts |
|
Conflicting PR. Removed from build DOCKER-merge#773. See the console output for more details.
--conflicts |
|
@sbesson : thoughts on the
or have server-base and server? |
|
Conflicting PR. Removed from build DOCKER-merge#777. See the console output for more details.
|
|
Discussed with @sbesson:
|
|
minimal concept pushed |
| # | ||
| services: | ||
| database: | ||
| image: "postgres:9.6" |
There was a problem hiding this comment.
Eventually, definitely. I'd suggest handling that across all repositories once the upgrade docs are in place.
| @@ -0,0 +1,10 @@ | |||
| #!/bin/bash | |||
There was a problem hiding this comment.
All the startup scripts are numbered to be run in order. "95" means "pretty close to the end but give the user a few slots (96-98) before the final script (99) runs.
There was a problem hiding this comment.
Thanks
since I noticed the pg version, for a minute I thought it was a pg matching version but the file was nothing to do with pg
|
Conflicting PR. Removed from build DOCKER-merge#941. See the console output for more details.
--conflicts |
This is based on the standalone image from https://github.com/ome/omero-web-docker/tree/5.6.0-m4 This just provides the infrastructure for building the extras image, it doesn't install or change anything (see ome#21 instead)
This is based on the standalone image from https://github.com/ome/omero-web-docker/tree/5.6.0-m4 This just provides the infrastructure for building the extras image, it doesn't install or change anything (see ome#21 instead)
This is based on the standalone image from https://github.com/ome/omero-web-docker/tree/5.6.0-m4 This just provides the infrastructure for building the extras image, it doesn't install or change anything (see ome#21 instead)
|
This pull request has been mentioned on Image.sc Forum. There might be relevant details there: https://forum.image.sc/t/how-to-install-omero-web-add-on-apps-with-docker/47434/3 |
|
Conflicting PR. Removed from build DOCKER-merge#1354. See the console output for more details.
--conflicts |
This branch started as a way to have files imported automatically on start as a proof-of-concept, but along with the work on ome/omero-web-docker#26 has become something of a grab bag of omero-server updates. Opening for discussion of the method and then we can split out the separate functionality if preferred.
Features include:
import-allscript (might should be unified with dropbox) (intended to be used-v data:/import)wait-on-loginfrom omero-test-infra (might should be migrated to core)--exclude