Reference conda and docker as installation methods. #5423
Conversation
Both conda and docker are great for certain use cases. So it is of benefit that these are mentioned in the docs.
cjllanwarne
added
Community Contribution
docs/Getting.md
Outdated
| You are strongly encouraged to use the latest release of Cromwell whenever possible. | ||
|
|
||
| Cromwell is distributed is a conda package on [conda-forge](https://conda-forge.org/). |
There was a problem hiding this comment.
OOI do you know who maintains the conda package for Cromwell? As someone who doesn't use conda, this seems like magic to me (and so I'm a little nervous about putting it in docs!)
If it's not automatic, could we say "Cromwell is also published with community support as a conda package ..."?
There was a problem hiding this comment.
The cromwell feedstock maintainers. That includes me.
Our job is very easy though. Every time there is a new Cromwell release, the conda-forge autotick bot will update the recipe and ping us. We just have to check the recipe and click the merge button. We have not had a not-working PR from the autotick bot yet. Since there are four of us, the conda package is usually published within a day. Plus the conda version comes with a great wrapper.
As long as the Cromwell team keeps the naming scheme of the JARs the same, it should be fully automatic. If you want, you could be added as recipe maintainer.
Both conda and docker are great for certain use cases. So it is of benefit that these are mentioned in the docs.
I removed "the preferred way is getting the jar" text because both the conda package and the docker container also contain the original jar. These are both way easier to use than a jar, so I would not recommend getting the jar over those two methods.