Dockstore provides a place for users to share tools encapsulated in Docker and described with the Common
Workflow Language (CWL), WDL (Workflow Description Language), Nextflow, or Galaxy. This enables scientists to share analytical
workflows so that they are machine readable as well as runnable in a variety of environments. While the
Dockstore is focused on serving researchers in the biosciences, the combination of Docker + workflow languages can be used by
anyone to describe the tools and services in their Docker images in a standardized, machine-readable way.
Dockstore is also a leading implementor of the GA4GH API standard for container registries, TRS.
For the live site see dockstore.org
This repo contains the web service and CLI components for Dockstore as well as collecting documentation and the issues for the project as a whole. The usage of this is to enumerate the docker containers (from quay.io and hopefully docker hub) and the workflows (from github/bitbucket) that are available to users of Dockstore.org.
For the related web UI see the dockstore-ui project.
The following section is useful for users of Dockstore (e.g. those that want to browse, register, and launch tools).
After registering at dockstore.org, you will be able to download the Dockstore CLI at https://dockstore.org/onboarding
A basic Dockstore configuration file is available/should be created in ~/.dockstore/config and contains the following
at minimum:
token = <your generated by the dockstore site>
server-url = https://www.dockstore.org/api
- Ensure that you are using Java 11. Java 8 (both Open and Oracle) will not work.
By default, cwltool reads input files from the local filesystem. Dockstore also adds support for additional file systems such as http, https, and ftp. Through a plug-in system, Dockstore also supports the Amazon S3, Synapse, and ICGC Storage Client via plugins.
Download the above set of default plugins via:
dockstore plugin download
Configuration for plugins can be placed inside the Dockstore configuration file in the following format
token = <your generated by the dockstore site>
server-url = https://www.dockstore.org/api
# options below this are optional
use-cache = false #set this to true to cache input files for rapid development
cache-dir = /home/<user>/.dockstore/cache #set this to determine where input files are cached (should be the same filesystem as your tool working directories)
[dockstore-file-synapse-plugin]
[dockstore-file-s3-plugin]
endpoint = #set this to point at a non AWS S3 endpoint
[dockstore-file-icgc-storage-client-plugin]
client = /media/large_volume/icgc-storage-client-1.0.23/bin/icgc-storage-client
Additional plugins can be created by taking one of the repos in plugins as a model and using pf4j as a reference. See additional documentation for more details.
The following section is useful for Dockstore developers (e.g. those that want to improve or fix the Dockstore web service and UI)
The dependency environment for Dockstore is described by our Travis-CI config. In addition to the dependencies for Dockstore users, note the setup instructions for postgres. Specifically, you will need to have postgres installed and setup with the database user specified in .travis.yml (ideally, postgres is need only for integration tests but not unit tests).
As an alternative to the following commands, if you do not have Maven installed you can use the maven wrapper as a substitute. For example:
./mvnw clean install
# instead of
mvn clean install
If you maven build in the root directory this will build not only the web service but the client tool:
mvn clean install
# or
mvn clean install -Punit-tests
If you're running tests on Travis-CI (or otherwise have access to the confidential data bundle) Run them via:
mvn clean install -Pintegration-tests
There are also certain categories for tests that they can be added to when writing new tests. Categories include:
ToilOnlyTestare tests that can only be run by Toil (which also installs a different version of cwltool)ToilCompatibleTestare tests that can be run with our default cwltool and with ToilConfidentialTestare tests that require access to our confidential testing bundle (ask a member of the development team if you're on the team)
You can also run it on your local computer but will need to setup postgres separately.
- Fill in the template dockstore.yml and stash it somewhere outside the git repo (like ~/.dockstore)
- The dockstore.yml is mostly a standard Dropwizard configuration file. Refer to the linked document to setup httpClient and database.
- Start with
java -jar dockstore-webservice/target/dockstore-webservice-*.jar server ~/.dockstore/dockstore.yml - If you need integration with GitHub.com, Quay.io. or Bitbucket for your work, you will need to follow the appropriate sections below and then fill out the corresponding fields in your dockstore.yml.
The Swagger UI is reachable while the Dockstore webservice is running. This allows you to explore available web resources.
codestyle.xml defines the coding style for Dockstore as an IntelliJ Code Style XML file that should be imported into IntelliJ IDE. We also have a matching checkstyle.xml that can be imported into other IDEs and is run during the build.
For users of Intellij or comparable IDEs, we also suggest loading the checkstyle.xml with a plugin in order to display warnings and errors while coding live rather than encountering them later when running a build.
Dockstore uses git-secrets to help make sure that keys and private data stay out of the source tree. For information on installing it on your platform check https://github.com/awslabs/git-secrets#id6 .
If you're on mac with homebrew use brew install git-secrets.
The dockstore command line should be installed in a location in your path.
/dockstore-client/bin/dockstore
You then need to setup a ~/.dockstore/config file with the following contents:
token: <dockstore_token_from_web_app>
server-url: http://www.dockstore.org:8080
If you are working with a custom-built or updated dockstore client you will need to update the jar in: ~/.dockstore/config/self-installs.
We use the swagger-codegen-maven-plugin to generate several sections of code which are not checked in. These include
- All of swagger-java-client (talks to our webservice for the CLI)
- All of swagger-java-quay-client (talks to Quay.io for our webservice)
- The Tool Registry Server components (serves up the TRS endpoints)
To update these, you will need to point at a new version of the swagger.yaml provided by a service. For example, update the equivalent of inputSpec in your branch.
Encrypted documents necessary for confidential testing are handled as indicated in the documents at Travis-CI for
files and environment variables.
A convenience script is provided as encrypt.sh which will compress confidential files, encrypt them, and then update an encrypted archive on GitHub. Confidential files should also be added to .gitignore to prevent accidental check-in. The unencrypted secrets.tar should be privately distributed among members of the team that need to work with confidential data. When using this script you will likely want to alter the CUSTOM_DIR_NAME. This is necessary since running the script will overwrite the existing encryption keys, instantly breaking existing builds using that key. Our current workaround is to use a new directory when providing a new bundle.
To add copyright headers to all files with IntelliJ
- Ensure the Copyright plugin is installed (Settings -> Plugins)
- Create a new copyright profile matching existing copyright header found on all files, name it Dockstore (Settings -> Copyright -> Copyright Profiles -> Add New)
- Set the default project copyright to Dockstore (Settings -> Copyright)
Additional documentation on developing Dockstore is available at legacy.md