Changes between Version 27 and Version 28 of HPC_deploy

Timestamp:

2015-11-19T00:40:03+01:00 (9 years ago)

Author:

Pieter Neerincx

Comment:

--

HPC_deploy

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