You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/getting_started/installation.rst
+19-7Lines changed: 19 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,16 +13,16 @@ Virtual Environment
13
13
===================
14
14
15
15
The recommended approach is to install from the repository directly, whether
16
-
you use pip or another setup approach. Here is how to clone the repository
17
-
and do a local install.
16
+
you use pip or another setup approach, and to install a `known release <https://github.com/singularityhub/singularity-hpc/releases/>`_. Here is how to clone the repository and do a local install.
or (an example with python setuptools and installing from the main branch)
26
26
27
27
.. code:: console
28
28
@@ -40,7 +40,7 @@ if you install to a system python, meaning either of these commands:
40
40
41
41
You will need to put the registry files elsewhere (update the ``registry`` config argument to the path), as they will not be installed
42
42
alongside the package. The same is the case for modules - if you install to system
43
-
python it's recomended to define ``lmod_base`` as something else, unless you
43
+
python it's recommended to define ``lmod_base`` as something else, unless you
44
44
can write to your install location. Installing locally ensures that you
45
45
can easily store your module files along with the install (the default until you
46
46
change it). Installation of singularity-hpc adds an executable, `shpc` to your path.
@@ -91,11 +91,23 @@ and interacting with your modules.
91
91
to install container modules.
92
92
93
93
94
+
Environment Modules
95
+
-------------------
96
+
97
+
If you are using `environment modules (tcl) <http://modules.sourceforge.net/>`_
98
+
and you find that your aliases do not expand, you can use `shopt <https://www.gnu.org/software/bash/manual/html_node/The-Shopt-Builtin.html>`_ to fix this issue:
99
+
100
+
.. code-block:: console
101
+
102
+
$ shopt expand_aliases || true
103
+
$ shopt -s expand_aliases
104
+
105
+
94
106
Pypi
95
107
====
96
108
97
-
The module is avaiable in pypi as `singularity-hpc <https://pypi.org/project/singularity-hpc/>`_,
98
-
and this is primairly to have a consistent means for release, and an interface to show the package. Since the registry
109
+
The module is available in pypi as `singularity-hpc <https://pypi.org/project/singularity-hpc/>`_,
110
+
and this is primarily to have a consistent means for release, and an interface to show the package. Since the registry
99
111
files will not install and you would need to change the registry path
100
112
and module base (making it hard to update from the git remote) we do not
101
113
encourage you to install from pip unless you know exactly what you are doing.
0 commit comments