I like the idea of using this repository to build and maintain Docker images that aren't provided nicely by biocontainers.
Looking over the current organization, I would suggest the following:
- Every active tool has a single
Dockerfile under their folder.
- Additional
Dockerfiles may be maintained in subfolders, but the one in the primary folder for the tool is the one which will be built in an automated way
- Automated Docker builds are configured to be triggered by tags following a regex. Example, the
cutadapt tool will be built from any GH push with a tag matching tag:cutadapt.*
- That way any updates to an individual tool can be captured as a hosted Docker image by making a release with the appropriate tag, e.g.
cutadapt-v1.0.0
I like the idea of using this repository to build and maintain Docker images that aren't provided nicely by
biocontainers.Looking over the current organization, I would suggest the following:
Dockerfileunder their folder.Dockerfilesmay be maintained in subfolders, but the one in the primary folder for the tool is the one which will be built in an automated waycutadapttool will be built from any GH push with a tag matchingtag:cutadapt.*cutadapt-v1.0.0