Accessing CVMFS/fr: Difference between revisions

Updating to match new version of source page
No edit summary
(Updating to match new version of source page)
Line 201: Line 201:
==== <tt>/opt/software/slurm/bin</tt>, <tt>/opt/software/bin</tt>, <tt>/opt/slurm/bin</tt> ====
==== <tt>/opt/software/slurm/bin</tt>, <tt>/opt/software/bin</tt>, <tt>/opt/slurm/bin</tt> ====
Ces chemins sont automatiquement ajoutés au <tt>PATH</tt> par défaut. Il permet l'ajout de votre exécutable dans le chemin de recherche.
Ces chemins sont automatiquement ajoutés au <tt>PATH</tt> par défaut. Il permet l'ajout de votre exécutable dans le chemin de recherche.
== Installing software locally ==
Since June 2020, we support installing additional modules locally and have it discovered by our central hierarchy. This was discussed and implemented in [this issue|https://github.com/ComputeCanada/software-stack/issues/11].
To do so, first identify a path where you want to install local software. For example <tt>/opt/software/easybuild</tt>. Make sure that folder exists. Then, export the environment variable <tt>RSNT_LOCAL_MODULEPATHS</tt>:
{{Command|export RSNT_LOCAL_MODULEPATHS{{=}}/opt/software/easybuild/modules}}
If you want this branch of the software hierarchy to be found by your users, we recommend you define this environment variable in the cluster's common profile. Then, install the software packages you want using EasyBuild:
{{Command|eb --installpath /opt/software/easybuild <some easyconfig recipe>}}
This will install the piece of software locally, using the hierarchical layout driven by our module naming scheme. It will also be automatically found when users load our compiler, MPI and Cuda modules.


=Mises en garde=
=Mises en garde=
38,789

edits