Skip to content

Commit

Permalink
doc: add intro and refine toc of index page
Browse files Browse the repository at this point in the history
  • Loading branch information
xdelaruelle committed Oct 15, 2017
1 parent cc3a854 commit a7dbbf2
Showing 1 changed file with 86 additions and 15 deletions.
101 changes: 86 additions & 15 deletions doc/source/index.rst
Original file line number Diff line number Diff line change
@@ -1,25 +1,96 @@
.. Modules documentation master file, created by
sphinx-quickstart on Mon Oct 2 06:17:09 2017.
You can adapt this file completely to your liking, but it should at least
contain the root `toctree` directive.
.. Home page
Welcome to Environment Modules' documentation!
===============================================
Environment Modules
===================

**Welcome to the Environment Modules documentation portal. The Environment
Modules package provides for the dynamic modification of a user's environment
via modulefiles.**

The Modules package is a tool that simplify shell initialization and
lets users easily modify their environment during the session with
modulefiles.

Each modulefile contains the information needed to configure the shell for
an application. Once the Modules package is initialized, the environment
can be modified on a per-module basis using the module command which
interprets modulefiles. Typically modulefiles instruct the module command
to alter or set shell environment variables such as ``PATH``, ``MANPATH``,
etc. modulefiles may be shared by many users on a system and users may
have their own collection to supplement or replace the shared modulefiles.

Modules can be **loaded** and **unloaded** dynamically and atomically,
in an clean fashion. All popular shells are supported, including *bash*,
*ksh*, *zsh*, *sh*, *csh*, *tcsh*, *fish*, as well as some scripting
languages such as *tcl*, *perl*, *python*, *ruby*, *cmake* and *r*.

Modules are useful in managing different versions of applications. Modules
can also be bundled into metamodules that will load an entire suite of
different applications.


Quick examples
--------------

Here is an example of loading a module on a Linux machine under bash.
::

$ module load gcc/6.1.1
$ which gcc
$ /usr/local/gcc/6.1.1/linux-x86_64/bin/gcc

Now we'll switch to a different version of the module
::

$ module switch gcc gcc/6.3.1
$ which gcc
/usr/local/gcc/6.3.1/linux-x86_64/bin/gcc

And now we'll unload the module altogether
::

$ module unload gcc
$ which gcc
gcc not found

Now we'll log into a different machine, using a different shell (tcsh).
::

% module load gcc/6.3.1
% which gcc
/usr/local/gcc/6.3.1/linux-aarch64/bin/gcc

Note that the command line is exactly the same, but the path has
automatically configured to the correct architecture.

.. toctree::
:maxdepth: 1
:hidden:
:maxdepth: 2
:caption: Installation

INSTALL
MIGRATING

.. toctree::
:hidden:
:maxdepth: 2
:caption: Man pages

modulefile
module
modulefile

.. toctree::
:hidden:
:maxdepth: 2
:caption: Additional information

diff_v3_v4
FAQ
MIGRATING
INSTALL
NEWS

Indices and tables
==================

* :ref:`genindex`
* :ref:`modindex`
* :ref:`search`
License
-------

Modules is distributed under the GNU General Public License version 2 (GPL
v2).

0 comments on commit a7dbbf2

Please sign in to comment.