Changes between Version 27 and Version 28 of HPC_deploy


Ignore:
Timestamp:
2015-11-19T00:40:03+01:00 (9 years ago)
Author:
Pieter Neerincx
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • HPC_deploy

    v27 v28  
    1212
    1313If you want to join the ''depad'' group, please [wiki:Contact contact the helpdesk].
    14 The depad group uses [https://hpcugent.github.io/easybuild/ EasyBuild], which uses !EasyConfigs as recipes to enforce consistent, reproducible installations.
     14The depad group uses [https://hpcugent.github.io/easybuild/ EasyBuild], which in turn uses !EasyConfigs as recipes to enforce consistent, reproducible installations.
    1515In a nutshell an !EasyConfig deployment recipe can handle the following steps:
    16161. (Bootstrap an installation and satisfy dependencies)
     
    2525
    2626The locations where we store source code, deployed apps, their accompanying module files, etc. are documented in the [wiki:HPC_storage#Software Storage SOP].
    27 !EasyBuild comes with !EasyConfigs for many our apps of interest ''out of the box''; These files are stored
     27!EasyBuild comes with !EasyConfigs for many of our apps of interest ''out of the box''; These files are stored
    2828* On our machines in a sub sub sub directory of where !EasyBuild was installed - Latest stable release we deployed.[[BR]]
    2929  The easiest way to find this directory is to load !EasyBuild and search for an app like this:
     
    5454
    5555If there is no existing !EasyConfig, we have to create one ourselves.
    56 
    57 First an example of an custom !EasyBuild file created for deploying our NGS_DNA pipeline. Below the code there will be the explanation of all the steps in the script.
     56First an example of a custom !EasyBuild file created for deploying our NGS_DNA pipeline.
     57Below the code there will be the explanation of all the steps in the recipe.
    5858{{{
    5959name = 'NGS_DNA'