Merge changes done via web interface.

.gitlab-ci.yml

@@ -14,10 +14,9 @@ workflow:
     - if: $CI_COMMIT_BRANCH == 'master'
 
 
-# To run deploy after build
 stages:
   - build
-  - deploy
+
 
 build:
   stage: build
@@ -32,28 +31,3 @@ build:
     - echo "{\"auths\":{\"$CI_REGISTRY\":{\"username\":\"$CI_REGISTRY_USER\",\"password\":\"$CI_REGISTRY_PASSWORD\"}}}" > /kaniko/.docker/config.json
     - /kaniko/executor --registry-mirror regmirror.embl.de --context $CI_PROJECT_DIR --dockerfile $CI_PROJECT_DIR/Dockerfile --destination $CI_REGISTRY_IMAGE:$CI_COMMIT_TAG
 
-deploy:
-  image: ubuntu:focal
-  stage: deploy
-  only:
-    - tags
-  script:
-    # Check if ssh-agent is present, install if not
-    - 'command -v ssh-agent >/dev/null || ( apt-get update -y && apt-get install openssh-client -y )'
-    # Run ssh-agent in the deploy environment
-    - eval $(ssh-agent -s)
-    # Add the SSH key from the SSH_PRIVATE_KEY variable to the agent store
-    # Use tr to fix line endings
-    - echo "$SSH_PRIVATE_KEY" | tr -d '\r' | ssh-add -
-    - mkdir -p ~/.ssh
-    - chmod 700 ~/.ssh
-    - ssh-keyscan cbbcs-01.embl.de >> ~/.ssh/known_hosts
-    - chmod 644 ~/.ssh/known_hosts
-    # Pull new container on server cbbcs-01
-    # User cbbcs needs to be member of the docker group
-    # to run the docker command
-    # Docker needs to log into the project's registry first
-    - ssh -o StrictHostKeyChecking=no cbbcs@cbbcs-01.embl.de "docker login -u gitlab-ci-token -p $CI_BUILD_TOKEN $CI_REGISTRY"
-    - ssh -o StrictHostKeyChecking=no cbbcs@cbbcs-01.embl.de "docker pull $CI_REGISTRY_IMAGE:$CI_COMMIT_TAG"
-    # Tag the new image as latest
-    - ssh -o StrictHostKeyChecking=no cbbcs@cbbcs-01.embl.de "docker image tag $CI_REGISTRY_IMAGE:$CI_COMMIT_TAG $CI_REGISTRY_IMAGE:latest"

README.md

@@ -6,7 +6,8 @@ Most bioimaging projects derive data from images and regions of interest (ROIs,
 Before you start, make sure that your data conforms to the requirements described in the [wiki section on preparing data for use with the IDE](https://git.embl.de/heriche/image-data-explorer/-/wikis/Preparing-the-data-for-use-with-the-IDE).  
 
 
-Don't want to install anything? Try our [ready-to-use cloud-based instance](https://shiny-portal.embl.de/shinyapps/app/01_image-data-explorer).  
+Don't want to install anything? Try our [ready-to-use cloud-based instance](https://shiny-portal.embl.de/shinyapps/app/01_image-data-explorer). 
+Note that when using cloud-based instances, images can only be accessed if they are in an S3-compatible object store.  
 
 Check our [2 min video introduction](videos/intro.mp4).