Right now the prevailing use case solved by Hydrant is that of starting directly from source code (e.g. Python, R, Bash, etc). But in many cases the code might be in various other forms:
- repository (e.g. on GitHub)
- tarball (e.g. from a collaborator)
- Dockerfile or equivalent (e.g. on DockerHub, BioContainers, etc)
We should brainstorm about how to handle this wider set of starting states and view it as one of the next biggest priorities; because external collaborators are starting to become more interested in using FireCloud, and many of them will already bring a Dockerfile (image) to the table, wrapping their code. Vicky's SignatureAnalyzer was an early attempt to explore this, and might be useful as an example to work against (since she has a method & config already functioning in FC that can be used as a baseline for comparison)
Right now the prevailing use case solved by Hydrant is that of starting directly from source code (e.g. Python, R, Bash, etc). But in many cases the code might be in various other forms:
We should brainstorm about how to handle this wider set of starting states and view it as one of the next biggest priorities; because external collaborators are starting to become more interested in using FireCloud, and many of them will already bring a Dockerfile (image) to the table, wrapping their code. Vicky's SignatureAnalyzer was an early attempt to explore this, and might be useful as an example to work against (since she has a method & config already functioning in FC that can be used as a baseline for comparison)