Summary
The nf-core pipelines you cloned, made searchable where they sit.
It reads the repositories already in your workspace rather than fetching anything, so a question about how rnaseq configures a step is answered from the copy you will actually run. Adding a pipeline means cloning it into the directory — nothing else registers it.
What it is
A navigator for nf-core pipeline repositories on disk: it lists the pipelines in your workspace, searches their files, and reports the modules a pipeline is built from.
What you get
- Every nf-core pipeline in the workspace, with its configuration file status
- Module information for a named pipeline
- Search across pipeline files, optionally scoped to one pipeline
- Pipeline config and workflow available as resources, addressed as pipeline://{name}/config and pipeline://{name}/workflow
- New pipelines detected automatically once cloned into the workspace directory
Requirements
A workspace directory holding cloned nf-core repositories — rnaseq, sarek, modules and any others you use. Node with npm run build, or the Docker image with the workspace mounted at /app/workspace.