This adds a parameter for specifying a local site config. Using --siteconf /path/to/conf and -profile sitename one can specify site specific configurations such as executors.
This could then also be a way for site to have even more involved settings regarding what outputs to produce or whatever.
I've also added 'site-conf' to .gitignore as a place to put such site-specific config files.
One could have used nextflow run -c /path/to/confbut it didn't feel as nice to use.
I would also be nice to have a exemple.config in site-conf as a way to show new sites a easy way to set up the pipeline for their local infrastructure.
sylvinite
commented
3 years ago
The purpose of the code changes are as follows:
This adds a parameter for specifying a local site config. Using
--siteconf /path/to/confand-profile sitenameone can specify site specific configurations such as executors. This could then also be a way for site to have even more involved settings regarding what outputs to produce or whatever.I've also added 'site-conf' to .gitignore as a place to put such site-specific config files.
One could have used
nextflow run -c /path/to/confbut it didn't feel as nice to use.I would also be nice to have a exemple.config in site-conf as a way to show new sites a easy way to set up the pipeline for their local infrastructure.