metavisitor-2 update process

[drosofff]

@ccedmendoza

• git clone https://github.com/ARTbio/GalaxyKickStart.git --branch metavisitor-2.0 in a freshly deployed instance with pip 1.9 and ansible==2.2 dependencies installed and docker installed (docker installation in script https://raw.githubusercontent.com/ARTbio/Run-Galaxy/master/deployment_scripts/install_docker.sh)

• navigate in GalaxyKickStart

• build the metavisitor image with docker build -t metavisitor .

• Run the docker image with

  export STANDARD=`docker run -d \
  -p 80:80 -p 21:21 -p 8800:8800 --tmpfs /var/run/ \
  --privileged=true \
  -e GALAXY_CONFIG_ALLOW_USER_DATASET_PURGE=True \
  -e GALAXY_CONFIG_ALLOW_LIBRARY_PATH_PASTE=True \
  -e GALAXY_CONFIG_ENABLE_USER_DELETION=True \
  -e GALAXY_CONFIG_ENABLE_BETA_WORKFLOW_MODULES=True \
  -v /tmp/:/tmp/ \
  -v /export/:/export \
  metavisitor`

• After a few second, the galaxy instance should be available on the port 80 of the VM (that should be enabled)

• From there, work on the imported workflows. Those that display correctly are those that are already upgraded. For the others, rebuild the workflow. Working on the corresponding workflow published in mississippi as template helps a lot. When a workflow is rebuild, download it locally. and push it in the local repo GalaxyKickStart in a work branch. The branch metavisitor-2 is protected. Do a pull request.

[drosofff]

@ccedmendoza close issue ?