2. Figure out dependencies/binaries/source code 3. Create a Dockerfile, build and test the built image + 4. Submit the request for a “new tool” 6. Design UI for your app and use it • CyVerse account (hAps://user.cyverse.org/register/) 5. Wait to hear from us
applica<on. • Dockerfile: Set of instruc<ons/commands that are used to build the Docker image. • CyVerse tools vs. apps: In the DE, a tool is an executable or binary upon which an app (an interface of a tool) is used to run the analyses.
program have? • Is the source code is already compiled? • If not, how to compile your source code ? • Best place to look is instruc<on manual • hAp://www.bioinforma<cs.babraham.ac.uk/projects/fastqc/
can use your tool in the Discovery Environment, a user interface must be defined. You will find your tool listed in the Tool Editor under the name “fastqc“ and version “0.11.5“. 5. Wait to hear from us
whistles • Avoid storing data inside of containers • Keep containers light and nimble, build on provided base images from trusted source • Do not trust a app without Dockerfile