nf-core
Restructure repo
Might break some stuff.
@jfy133 anythoughts on moving to a structure similar to the modules repo?
$ tree conf/utd_ganymede/
conf/utd_ganymede/
├── utd_ganymede.config
└── utd_ganymede.md
Maybe a better example
$ tree conf/uppmax/
conf/uppmax/
├── README.md
├── pipeline
│ ├── ampliseq.config
│ └── ampliseq.md
└── uppmax.config
Could nest the ampliseq one more time too.
Theoretically no reason not to, but it would break the website rendering currently I imagine.
What would the benefits be though?
I don't see an issue between configs/modules having different structures because they are entirely different things
Benefit would be it might be easier to find stuff, and see what's supported for a given HPC system.
Most users have access to one or a few of the systems in this list, and they probably want to find what pipelines are supported, not the other way around, of one person looking to run one pipeline across multiple systems.
I think it feels written from the perspective of pipeline developers, when in reality I think this repo is for users/admins of these systems.
I think it feels written from the perspective of pipeline developers, when in reality I think this repo is for users/admins of these systems.
How did you guess? I did really create that for me, for a certain pipeline as a pipeline developer...
Then let's wait for @mashehu to come back from baby-ing so we don't accidently break the website
@edmundmiller let's make it a hackathon task and collaborate with @mashehu not to break anything