Fred Hutch keeps EasyBuild recipes in github. I also publish an index to all the Scientific software in the same Github repo using Github Pages. Our custom R and Python are extensions of the basic R and Python EasyConfigs are are documented using "easy_anotate". As users ask questions about Easybuild we have been adding to our local documentation. Why are the modules called foss? https://fredhutch.github.io/easybuild-life-sciences/toolchains/ Basic use of modules etc. As new new modules are created they are checked in and documented with "create_update.sh". Which creates blog types posts: https://fredhutch.github.io/easybuild-life-sciences/updates/. A git trigger sends the updates to a Fred Hutch Slack page for BioInformatics.
Fred Hutch Life Sciences Software: https://fredhutch.github.io/easybuild-life-sciences/ Fully annotated R module: https://fredhutch.github.io/easybuild-life-sciences/r/fhR-4.1.0-foss-2020b/ the scripts to create the site are in the "scripts" directory. John Dey [email protected] On Sat, Sep 18, 2021 at 5:51 PM Lev Lafayette <[email protected]> wrote: > Hi Easybuilders, > > Where do you store your notes for modifications for fine-tuning > Easybuild recipes? For example, using specific hardware nodes for > particular builds? > > Do you keep them in a git repository as issues? In the recipe > directory? Or as comments in the recipe file itself? > > Is there a convention within the community, or should there be one? > > Our site has competing schools of thought, so we're asking the wider > community for what you all do. :) > > All the best, > > > -- > Lev Lafayette <[email protected]> >
