Internal: Add modulefiles used for installations on various machines

[jprestop]

Describe the Task

Add the modulefiles used for installations on various machines to the repository for reference and backup, to internal/scripts/installation/modulefiles.

Time Estimate

< 1 day of work

Sub-Issues

Consider breaking the task down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

NONE

Funding Source

2792541

Define the Metadata

Assignee

• Select engineer(s) or no engineer required
• Select scientist(s) or no scientist required

Labels

• Select component(s)
• Select priority
• Select requestor(s)

Projects and Milestone

• Select Repository and/or Organization level Project(s) or add alert: NEED PROJECT ASSIGNMENT label
• Select Milestone as the next official version or Future Versions

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdataio, METviewer, METexpress, METcalcpy, METplotpy

Task Checklist

See the METplus Workflow for details.

• Complete the issue definition above, including the Time Estimate and Funding Source.
• Fork this repository or create a branch of develop.
  Branch name: feature_<Issue Number>_<Description>
• Complete the development and test your changes.
• Add/update log messages for easier debugging.
• Add/update unit tests.
• Add/update documentation.
• Add any new Python packages to the METplus Components Python Requirements table.
• Push local changes to GitHub.
• Submit a pull request to merge into develop.
  Pull request: feature <Issue Number> <Description>
• Define the pull request metadata, as permissions allow.
  Select: Reviewer(s) and Linked issues
  Select: Repository level development cycle Project for the next official release
  Select: Milestone as the next official version
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.

[georgemccabe]

This work should be done at the same time as or shortly after #1748

[jprestop]

@georgemccabe I have completed the work in a branch. I wasn't sure why it needed to be done at the same time or after #1748, but I can wait to submit the PR (doing a pull from develop once #1748 is done) if you'd like.

[georgemccabe]

@jprestop, I suppose it doesn't need to be done with #1748, but there will be both internal and internal_tests directories if you merge your changes before the other issue is completed. That shouldn't be a problem though.

[jprestop]

@georgemccabe Thanks. I went ahead and submitted a PR and assigned you as the reviewer. No rush.