Arvados

1. New cwlviewer docker container will be published to docker hub
2. Trigger via "push" (the publisher process logs into view.commonwl.org and triggers update) or "pull" (cron job checks for new container image)
3. Pull new container image from docker hub
4. Restart service with new container image, but using existing volumes that contain the database

=======================================================================================

The cwlviewer service runs with docker compose, with the docker images built locally from source. There are three containers involved.

The plan:

• add a -dev instance (cwlviewer-dev.arvados.org), also running with composer, images built from source, that just gets updated whenever the git tree is (main). Ideally this happens somehow via Jenkins (so that non-sysadmins can see it happen and there is a record of the updated deploy).

• for the production instance, add a Jenkins job that can be used to update the running copy (i.e. specifying a git commit hash, for a release published on github, ideally). This job can be triggered manually as needed.