Private Nextflow module registry with GitHub pull-through
acknowledged
Rob Newman
Enterprise users need a private, self-hosted Nextflow module registry that supports pull-through from private GitHub repositories with authentication (PAT or app-based).
The registry should allow organizations to centralize internal pipeline modules, support bulk import from one or multiple GitHub repos, and be deployable within the customer's network (Kubernetes/EKS preferred).
Drew DiPalma
Merged in a post:
Allow Private Plugin hosting
Florian Wuennemann
Will it be possible for users to host their own registry to deploy private plugins in their org?
Rob Newman
Merged in a post:
Internal Nextflow module system/registry to improve pipeline development
C
Canny AI
We need an internal Nextflow module system or registry to avoid repetitive coding and errors in pipeline development. This would help streamline our development process and reduce debugging time.
Rob Newman
updated the status to
acknowledged
Rob Newman
Merged in a post:
Internally-hosted Nextflow plugin registry
C
Canny AI
I would like the ability to host an internally-hosted version of the Nextflow plugin registry, similar to how Terraform allows for an internal registry. This would help manage Nextflow plugins that are specific to our internal infrastructure and business logic.