-
Notifications
You must be signed in to change notification settings - Fork 312
Add EVA GRACE cluster #915
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
base: master
Are you sure you want to change the base?
Conversation
@nf-core-bot fix linting |
enabled = true | ||
autoMounts = true | ||
// TODO have IT make a generic one shared storage available | ||
cacheDir = "/mnt/archgen/tools/singularity/containers/" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The usual "are your really sure your don't want libraryDir
here?" :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For now I've copied over just from the (very) old EVA cluster as it's the same but should update it.
But yes, we should probably write some guidelines on this...
How would you guide/direct people in this? We could make some config specifications/best practises like the modules/pieplines/test-data etc here: https://nf-co.re/docs/guidelines/components/overview
@TCLamnidis do you want to try/test before I merged? (after updating the libraryDir thing once Pontus and I write some docs) |
@nf-core-bot fix linting |
name: New Config
about: A new cluster config
Local testing succesful ✅
Please follow these steps before submitting your PR:
[WIP]
in its titlemaster
branchSteps for adding a new config profile:
conf/
directorydocs/
directorynfcore_custom.config
file in the top-level directoryprofile:
scope in.github/workflows/main.yml
.github/CODEOWNERS
(**/<custom-profile>** @<github-username>
)