Implement container_register for tool repositories.#675
Implement container_register for tool repositories.#675jmchilton merged 1 commit intogalaxyproject:masterfrom
Conversation
|
Is it worth fixing the typo in the commit message? |
|
The documentation is somewhat cryptic without being familiar with the area, but that also means I can't suggest how to improve this: """Register multi-requirement containers as needed.
BioContainers publishes all Bioconda packages automatically as individual
container images. These however are not enough for tools with multiple
best-practice requirements. Such requirements should be recorded and published
so that a container can be created and registered for these tools.
""" |
2bb46c3 to
49df20e
Compare
49b03d3 to
8de4bb8
Compare
|
@peterjc Agreed this is not documented well and I'm still trying to figure out how to describe what is going on. There was a bit of a conversation about this in the tools-iuc Gitter just now and there is some discussion on the README of this repo if you want to dig a little deeper. At a high level, the goal is that all tools that have Conda-ified requirement tags will automatically have containers registered and published quay.io/biocontainers for each unique combination of requirements. This new command opens a PR against a registry of such combinations that when merged will result in a container being published. I want to just monitor repositories though and take care of these details without intervention on a per tool basis - so to leverage this tool developers will just need to add their repository to the list in this file (https://github.com/jmchilton/mulled-monitor/blob/master/monitor.sh#L3). I'm going to present this as the GCC - so hopefully I figure out how to talk about this before then. |
f9dd933 to
653ab43
Compare
Along with associated enhancements to Github, Conda, and mulled utilities.
e07aa3d to
44a0a7c
Compare
|
Wuhu!!!! |
|
Thanks @bgruening - I've updated #646 with your v2 mulled idea. |
xref - last bullet of #646