diff --git a/.zenodo.json b/.zenodo.json index 20de1a45a..066504b26 100644 --- a/.zenodo.json +++ b/.zenodo.json @@ -239,6 +239,11 @@ "affiliation": "National Eye Institute, National Institutes of Health, USA", "orcid": "0000-0002-4579-003X" }, + { + "name": "Kuhlmann, Justus Theodor", + "affiliation": "Universität Münster", + "orcid": "0000-0001-5291-1939" + }, { "name": "Hanke, Michael", "affiliation": "Institute of Neuroscience and Medicine, Brain & Behaviour (INM-7), Research Centre Jülich, Jülich, Germany and Institute of Systems Neuroscience, Medical Faculty, Heinrich Heine University Düsseldorf, Düsseldorf, Germany", diff --git a/docs/beyond_basics/101-169-cluster.rst b/docs/beyond_basics/101-169-cluster.rst index 4b99659d6..04e540748 100644 --- a/docs/beyond_basics/101-169-cluster.rst +++ b/docs/beyond_basics/101-169-cluster.rst @@ -18,6 +18,8 @@ DataLad installation on a cluster Users of a compute cluster generally do not have administrative privileges (sudo rights) and thus cannot install software as easily as on their own, private machine. In order to get DataLad and its underlying tools installed, you can either `bribe (kindly ask) your system administrator `_ [#f1]_ or install everything for your own user only following the instructions in the paragraph :ref:`norootinstall` of the :ref:`installation page `. +If you opt for the first, your administrator can install Datalad version 0.18.4 via `EasyBuild `, which is a tool for building software reprobucibly and is common on clusters that use a module system. +The caveat this introduces, of course, is that you will need to load the module every time you want to use DataLad on your cluster. .. rubric:: Footnotes