Skip to content

zavolanlab/Dockerfiles

Folders and files

NameName
Last commit message
Last commit date

Latest commit

5212974 · Jul 8, 2022
Mar 20, 2020
Jul 13, 2018
May 15, 2018
May 25, 2018
Jan 20, 2020
Apr 6, 2021
Jul 13, 2018
Nov 18, 2020
Jul 23, 2018
Apr 15, 2019
Feb 19, 2019
May 22, 2018
Jun 26, 2020
Jul 17, 2018
Nov 26, 2018
Apr 2, 2020
Feb 21, 2020
Jan 20, 2020
Apr 7, 2020
Jul 23, 2018
Sep 29, 2019
Mar 20, 2020
May 25, 2018
Feb 5, 2019
Jan 8, 2020
Feb 22, 2021
Jul 19, 2018
May 17, 2018
Feb 21, 2020
Feb 21, 2020
Mar 11, 2020
Mar 6, 2020
Apr 7, 2020
Feb 21, 2020
Jun 18, 2020
Dec 16, 2021
Jan 5, 2022
Jul 17, 2018
Jan 24, 2020
Jul 17, 2018
Aug 22, 2020
Jul 8, 2022
Aug 13, 2021
Jan 16, 2019
Jul 22, 2019
Jan 4, 2022
Jan 22, 2020
Feb 21, 2020
Feb 6, 2019
Feb 21, 2020
Mar 30, 2021
May 15, 2018
Oct 29, 2018
Oct 19, 2018
Feb 18, 2019
Jun 8, 2018
Jun 5, 2018
Jun 5, 2018
Feb 11, 2019
Oct 17, 2018
May 15, 2018
Apr 6, 2021
Jan 9, 2020
Jan 9, 2020
Jan 9, 2020
Jan 9, 2020
Jan 9, 2020

Repository files navigation

License Build_status

Zavolan lab Dockerfile repository

Contains recipes for building Docker images for bioinformatics tools. The main focus is on scripts/tools built within the Zavolan lab, but third-party tools are also included, if no well-maintained official image repository exists (or has existed at the time of creation) for these tools.

The corresponding images can be found on the lab's Docker Hub space.

Contributing

Your contributions are highly appreciated!

To add a Dockerfile for a new tool or a different version of an existing tool, please follow these simple rules:

  1. If you are already a member of the zavolanlab organization here on GitHub, please clone the repository and create a feature branch off of branch master (see Git Flow for details on why/how to do that). If you are an external contributor, please fork the repository instead.
  2. Please create a new directory with the tool's name and/or version. It is important that you stick to the directory structure/naming conventions: <root_dir>/<tool_name>/<version>/Dockerfile. If you are unsure, have a look at some of the existing examples.
  3. In order to reduce image size and possible security risks, try to only add software that is required to run the tool and follow best practices for writing Dockerfiles. Do not forget to include relevant metadata as well (have a look at the existing examples).
  4. Document your code and update all relevant documentation, if necessary. Add your name and GitHub profile URL to the list of contributors.
  5. Issue a pull request (PR). Upon filing, images are automatically built for all new and modified Dockerfiles within the scope of the PR. PRs are not merged into the main branch (master) unless this check passes and at least one member of the Zavolan lab approves of the PR. Once merged, images are automatically pushed to the lab's Docker Hub space.

For more information (particularly if you have are new to Git/GitHub) or other ways of how you can contribute, please take a look at the contributor instructions.

License

This project is covered by the Apache License 2.0 also shipped with this repository.