Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auto import, figure, wheel, etc. #21

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

joshmoore
Copy link
Member

@joshmoore joshmoore commented Jan 30, 2019

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:

  • Add an import-all script (might should be unified with dropbox) (intended to be used -v data:/import)
  • Migrate wait-on-login from omero-test-infra (might should be migrated to core)
  • Enable figure by default
  • Use ice_python_wheel
  • public user

--exclude

@joshmoore joshmoore changed the title Auto import, etc. Auto import, figure, wheel, etc. Jan 30, 2019
@joshmoore
Copy link
Member Author

joshmoore commented Jan 30, 2019

Downloaded Figure PDF of auto-imported fake:

Figure_2019-1-30_15-5-3.pdf

cc: @pwalczysko

@snoopycrimecop
Copy link
Member

Conflicting PR. Removed from build DOCKER-merge#667. See the console output for more details.
Possible conflicts:

--conflicts

@sbesson
Copy link
Member

sbesson commented Mar 15, 2019

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 --transfer=ln_s to prevent data copy as the files are imported from the server directly.

Happy to see this functionality extracted to a dedicated PR and sign off on it.

@snoopycrimecop
Copy link
Member

Conflicting PR. Removed from build DOCKER-merge#711. See the console output for more details.
Possible conflicts:

--conflicts

@snoopycrimecop
Copy link
Member

Conflicting PR. Removed from build DOCKER-merge#712. See the console output for more details.
Possible conflicts:

--conflicts

@snoopycrimecop
Copy link
Member

Conflicting PR. Removed from build DOCKER-merge#713. See the console output for more details.
Possible conflicts:

--conflicts

@manics
Copy link
Member

manics commented Mar 18, 2019

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

@snoopycrimecop
Copy link
Member

Conflicting PR. Removed from build DOCKER-merge#714. See the console output for more details.
Possible conflicts:

--conflicts

@snoopycrimecop
Copy link
Member

Conflicting PR. Removed from build DOCKER-merge#773. See the console output for more details.
Possible conflicts:

--conflicts

@joshmoore
Copy link
Member Author

@sbesson : thoughts on the kitchensink approach, and if so, any suggestions for a name? (since "standalone" doesn't quite work)

  • server-advanced
  • server-extended
  • server-public + server-import (but what if you want both??)

or have server-base and server?

@snoopycrimecop
Copy link
Member

snoopycrimecop commented May 22, 2019

Conflicting PR. Removed from build DOCKER-merge#777. See the console output for more details.
Possible conflicts:

--conflicts Conflict resolved in build DOCKER-merge#778. See the console output for more details.

@joshmoore
Copy link
Member Author

joshmoore commented May 22, 2019

Discussed with @sbesson:

  • server-minimal & server suggested as the first step
  • Makefile could move to build-infra (eventually to scc)
  • add public user in extended verison

@joshmoore
Copy link
Member Author

minimal concept pushed

#
services:
database:
image: "postgres:9.6"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldn't it be moved to 10?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Eventually, definitely. I'd suggest handling that across all repositories once the upgrade docs are in place.

@@ -0,0 +1,10 @@
#!/bin/bash
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does 95 mean in the name?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@snoopycrimecop
Copy link
Member

Conflicting PR. Removed from build DOCKER-merge#941. See the console output for more details.
Possible conflicts:

  • Upstream changes
    • playbook.yml

--conflicts

manics added a commit to manics/omero-server-docker that referenced this pull request Dec 12, 2019
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)
manics added a commit to manics/omero-server-docker that referenced this pull request Jun 4, 2020
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)
manics added a commit to manics/omero-server-docker that referenced this pull request Sep 17, 2020
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)
@imagesc-bot
Copy link

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

@snoopycrimecop
Copy link
Member

Conflicting PR. Removed from build DOCKER-merge#1354. See the console output for more details.
Possible conflicts:

  • Upstream changes
    • playbook.yml

--conflicts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants