Hi folks, I'm trying to understand how my teams' s...
# modules
n
Hi folks, I'm trying to understand how my teams' software needs should translate into a nextflow solution. We have a bunch of custom modules and subworkflows we have written and pipelines that call them but there's a bit of duplication. I would really love to have a centralized repository that maintains: 1. The custom modules we've written 2. The subworkflows we have written built off a combination of these custom modules and standard nf-core modules I think this pattern would enable the other pipelines we have to be able to install these common components as needed. It looks like
repository_type: modules
will not suite my needs as I'll have an orgniazation module directory and an nf-core one (if I'm understanding the pattern correctly) so would I need to use
repository_type: pipeline
for this repository? Since it's built on multiple module sources?
j
Hi @Nabil Azamy, having subworkflows build with modules from mixed sources is not supported at the moment
we are though working on this, with some opened PRs already https://github.com/nf-core/tools/pull/3083
n
Nice to meet you Julia! Thank you so much for the pointer. This makes sense and seems to be consistent with the need I'm describing. I'll follow the PR along. I'm seeing that nf-core has the following projects: https://github.com/orgs/nf-core/projects?query=is%3Aopen where the PR you linked is pointing to the nf-core infrastructure one. Is there anyone else I can look at to get a "bigger" picture?
j
the developement of nf-core/tools happens at https://github.com/nf-core/tools you can see all issues, PRs and release milestones there
n
Thank you!