Add Environment Modules to Build and software organization tools

[xdelaruelle]

Reintroduce Environment Modules software which was removed by 7f947f8. Removal was due to the project being hosted on SourceForge. Project is now primarily managed from GitHub.

Also take this opportunity to clarify name of Lmod software (in the same category).

Thank you for taking the time to work on a PR for Awesome-Sysadmin!

To ensure your PR is dealt with swiftly please check the following:

• Your additions are Free software
• Software your are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts).
• Submit one item per pull request. This eases reviewing and speeds up inclusion.
• Format your submission as follows, where Demo and Clients are optional.
  Do not add a duplicate Source code link if it is the same as the main link.
  Keep the short description under 80 characters and use sentence case
  for it, even if the project's webpage or readme uses another capitalisation.
  Demo links should only be used for interactive demos, i.e. not video demonstrations.
  - [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language`
• Additions are inserted preserving alphabetical order.
• Additions are not already listed at awesome-selfhosted
• The Language tag is the main server-side requirement for the software. Don't include frameworks or specific dialects.
• You have searched the repository for any relevant issues or PRs, including closed ones.
• Any category you are creating has the minimum requirement of 3 items.
• Any software project you are adding to the list is actively maintained.
• The pull request title is informative, unlike "Update README.md".
  Suggested titles: "Add aaa to bbb" for adding software aaa to section bbb,
  "Remove aaa from bbb" for removing, "Fix license for aaa", etc.

---

Please take some time to answer the following questions as best you can:

• Why is it awesome?

Environment Modules helps to manage large software catalog and provide various versions of the same software. It is a tool coming from the HPC world and deployed on most supercomputers to help their user to handle their software set.

• Have you used it? For how long?

I use it since 15 years

• Is this in a personal or professional setup?

You can use this software either on your local laptop or on a supercomputer environment. So it may be used on both setup kind.

• How many devices/users/services/... do you manage with it?

Environment Modules enables software in user environment. With this tool sysadmins in HPC centers usually provides 1000x of software to their users through this tool.

• Biggest pros/cons compared to other solutions?

Environment Modules was first released in 1991. Since then other implementation of the module concept were published. Most popular of these alternatives is Lmod which is also listed here.

Environment Modules is actively developed, tested and provides advanced features like dependency resolution of the modulefiles to load in user environment.

Biggest cons is that the modulefiles are written in Tcl, which is a scripting language people are often afraid of. But as soon as they overcome this initial fear, writing modulefiles is quite easy (this is just simple Tcl scripts).

• Any other comments about your use case, things you've found excellent, limitations you've encountered... ?

Nothing more

[nodiscc]

Interesting