Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[biocterm] [biocswirl] Implement contained installations #6

Open
1 of 2 tasks
lisancao opened this issue May 21, 2020 · 0 comments
Open
1 of 2 tasks

[biocterm] [biocswirl] Implement contained installations #6

lisancao opened this issue May 21, 2020 · 0 comments
Labels
enhancement New feature or request priority

Comments

@lisancao
Copy link
Contributor

lisancao commented May 21, 2020

[biocterm] [biocswirl] Implement contained installations

About: Installations are currently pretty messy, particularly with R as going through a course will install a LOT of packages, and it's unclear whether swirl has a clean uninstall feature. As we work on multilanguage workflows it becomes more and more important for us to have contained environments for courses, especially if our installs overwrite packages someone already has. Should also prompt user if they want to use their install or keep it contained.

Tasks

  • Explore options of either using Docker or Singularity Containers (multilanguage workflows) or working with beRi (Bioconductor workflows)
  • Prepare singularity recipes for respective courses (will also have to use Rocker) and execute from BiocTerm

Resources

https://singularity.lbl.gov/

(Workflow managers)
Nextflow
https://www.commonwl.org/v1.0/CommandLineTool.html

Tag can be

biocswirl(related to course material)
biocterm (interface changes)
dev      (developers only)
file     (changes to file and folder structuring) 
rpkg     (r package/usethis and CRAN documentation changes)
feat     (new feature)
fix      (bug fix)
refactor (refactoring code)
style    (formatting, missing semi colons, etc; no code change)
doc      (changes to documentation)
test     (adding or refactoring tests; no production code change)
version  (version bump/new release; no production code change)
dbg      (Changes in debugging code/frameworks; no production code change)
license  (Edits regarding licensing; no production code change)
hack     (Temporary fix to make things move forward; please avoid it)
WIP      (Work In Progress; for intermediate commits to keep patches reasonably sized)
@lisancao lisancao added enhancement New feature or request priority labels May 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority
Projects
None yet
Development

No branches or pull requests

1 participant