NASA-AMMOS SLIM Repository Essentials Assistance -- Baseline Files

.dockerignore

@@ -1,6 +1,11 @@
-node_modules
-npm-debug.log
-API/node_modules
-Missions
-Missions_rel
-Missions_dev
+node_modules
+npm-debug.log
+API/node_modules
+Missions
+Missions_rel
+Missions_dev
+.env
+**/.git
+data
+*DS_Store
+*__pycache__

.eslintignore

@@ -0,0 +1,7 @@
+node_modules
+npm-debug.log
+API/node_modules
+Missions
+Missions_rel
+Missions_dev
+src/external

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,43 @@
+---
+name: Bug Report
+about: Report a bug to help us improve
+title: '[Bug]: '
+labels: 'bug'
+assignees: ''
+
+---
+
+**Checked for duplicates**
+
+> Have you checked for duplicate issue tickets?
+
+- Ex. Yes - I've already checked
+- Ex. No - I haven't checked
+
+**Describe the bug**
+
+> A clear and concise description of what the bug is. Plain-text snippets preferred but screenshots welcome.
+
+Ex. When I did [...] action, I noticed [...]
+
+**What did you expect?**
+
+> A clear and concise description of what you expect to happen
+
+Ex. I expected [...]
+
+**Reproducible steps**
+
+> How would we reproduce this bug? Please walk us through it step by step. Plain-text snippets preferred but screenshots welcome.
+
+1.
+2.
+3.
+
+**What is your environment?**
+
+> Include any computer hardware, operating system, framework, browser, time-of-day or other contextual information related to your issue
+
+- Ex. Version of this software [e.g. vX.Y.Z]
+- Ex. Operating System: [e.g. MacOSX with Docker Desktop vX.Y]
+- ...

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,59 @@
+name: Bug Report Form
+description: Report a bug to help us improve
+title: "[Bug]: "
+labels: "bug"
+body:
+  - type: markdown
+    attributes:
+      value: |
+        > _Thanks for filing a bug ticket. We appreciate your time and effort. Please answer a few questions._
+  - type: dropdown
+    id: checked-for-duplicates
+    attributes:
+      label: Checked for duplicates
+      description: Have you checked for duplicate issue tickets?
+      multiple: false
+      options:
+        - "Yes - I've already checked"
+        - "No - I haven't checked"
+    validations:
+      required: yes
+  - type: textarea
+    id: description
+    attributes:
+      label: Describe the bug
+      description: A clear and concise description of what the bug is. Plain-text snippets preferred but screenshots welcome.
+      placeholder: Tell us what you saw
+      value: "When I did [...] action, I noticed [...]"
+    validations:
+      required: true
+  - type: textarea
+    id: expected-behavior
+    attributes:
+      label: What did you expect?
+      description: A clear and concise description of what you expect to happen
+      placeholder: Tell us what you expected
+      value: "I expected [...]"
+    validations:
+      required: true
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Reproducible steps
+      description: "How would we reproduce this bug? Please walk us through it step by step. Plain-text snippets preferred but screenshots welcome."
+      value: |
+        1.
+        2.
+        3.
+        ...
+      render: bash
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment
+      description: "What is your environment? Include any computer hardware, operating system, framework, browser, time-of-day or other contextual information related to your issue"
+      value: |
+        - Version of this software [e.g. vX.Y.Z]
+        - Operating System: [e.g. MacOSX with Docker Desktop vX.Y]
+        ...
+      render: bash

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,34 @@
+---
+name: New Feature
+about: Suggest a new feature for us to implement
+title: '[New Feature]: '
+labels: 'enhancement'
+assignees: ''
+
+---
+
+**Checked for duplicates**
+
+> Have you checked for duplicate issue tickets?
+
+- Ex. Yes - I've already checked
+- Ex. No - I haven't checked
+
+**Alternatives considered**
+
+> Have you considered alternative solutions to your feature request?
+
+- Ex. Yes - and alternatives don't suffice
+- Ex. No - I haven't considered
+
+**Related problems**
+
+> Is your feature request related to any problems? Please help us understand if so, including linking to any other issue tickets.
+
+Ex. I'm frustrated when [...] happens as documented in issue-XYZ
+
+**Describe the feature request**
+
+> A clear and concise description of your request. 
+
+Ex. I need or want [...]

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,48 @@
+name: New Feature Form
+description: Suggest a new feature for us to implement
+title: "[New Feature]: "
+labels: "enhancement"
+body:
+  - type: markdown
+    attributes:
+      value: |
+        > _Thanks for filing a new feature request. We appreciate your time and effort. Please answer a few questions._
+  - type: dropdown
+    id: checked-for-duplicates
+    attributes:
+      label: Checked for duplicates
+      description: Have you checked for duplicate issue tickets?
+      multiple: false
+      options:
+        - "Yes - I've already checked"
+        - "No - I haven't checked"
+    validations:
+      required: yes
+  - type: dropdown
+    id: checked-alternatives
+    attributes:
+      label: Alternatives considered
+      description: Have you considered alternative solutions to your feature request?
+      options:
+        - "Yes - and alternatives don't suffice"
+        - "No - I haven't considered"
+    validations:
+      required: yes
+  - type: textarea
+    id: related-problems
+    attributes:
+      label: Related problems
+      description: Is your feature request related to any problems? Please help us understand if so, including linking to any other issue tickets.
+      placeholder: Tell us the problems
+      value: "I'm frustrated when [...] happens as documented in issue-XYZ"
+    validations:
+      required: false
+  - type: textarea
+    id: description
+    attributes:
+      label: Describe the feature request
+      description: A clear and concise description of your request. 
+      placeholder: Tell us what you want
+      value: "I need or want [...]"
+    validations:
+      required: true

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,13 @@
+## Purpose
+- Clear, easy-to-understand sentences outlining the purpose of the PR
+## Proposed Changes
+- [ADD] ...
+- [CHANGE] ...
+- [FIX] ...
+## Issues
+- Links to relevant issues
+- Example: issue-XYZ
+## Testing
+- Provide some proof you've tested your changes 
+- Example: test results available at ...
+- Example: tested on operating system ...

.github/workflows/docker-build.yml

@@ -0,0 +1,117 @@
+name: Docker build and push
+
+# limit concurrency
+# https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#examples-using-concurrency-and-the-default-behavior
+concurrency: docker_mmgis_main
+
+on:
+  push:
+    # Only activate for `master` branch
+    branches:
+      - master
+      - development
+    # Plus for all tags
+    tags:
+      - "*"
+
+  # Plus for any pull-requests
+  pull_request:
+    branches:
+      - master
+      - development
+
+  # And for any final releases
+  release:
+    types: [published]
+
+env:
+  # Will be "NASA-AMMOS/MMGIS" for the main repo, for forks "user-name-of-fork/MMGIS"
+  # For generating the tag, all will be converted to lowercase
+  IMAGE_SLUG: ${{ github.repository }}
+
+jobs:
+  # Push image to GitHub Container Registry.
+  # The image tag pattern is:
+  # for pull-requests: <PATCH_VERSION>-<DATE>-<PR_NUMBER>, eg: 1.35.2-20210125-25
+  # for tags: <TAG>
+  # for `master` branch: latest,<PATCH_VERSION>-latest,<MINOR_VERSION>-latest,<MAJOR_VERSION>-latest,<PATCH_VERSION>-<DATE>-<SHA>
+  # for `development` branch: development,<MAJOR_VERSION>-development,<PATCH_VERSION>-<DATE>-<SHA>
+  # for releases: release,<PATCH_VERSION>-release,<MINOR_VERSION>-release,<MAJOR_VERSION>-release,<PATCH_VERSION>-<DATE>-<SHA>
+  # Version is parsed from package.json
+  push:
+    runs-on: ubuntu-latest
+    if: github.event_name == 'push' || github.event_name == 'pull_request' || github.event_name == 'release'
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3
+
+      - name: Generate tags
+        id: generate
+        run: |
+
+          # Image ID
+          IMAGE_ID=ghcr.io/$IMAGE_SLUG
+
+          # Date
+          BDATE=$(date +%Y%m%d)
+
+          # PATCH_VERSION from package.json is like "1.2.3"
+          # MINOR_VERSION like "1.2", MAJOR_VERSION like "1"
+          PATCH_VERSION=$(jq .version -r ./package.json)
+          MINOR_VERSION=${PATCH_VERSION%.*}
+          MAJOR_VERSION=${MINOR_VERSION%.*}
+
+          # Change all uppercase to lowercase, just in case
+          IMAGE_ID=$(echo $IMAGE_ID | tr '[A-Z]' '[a-z]')
+
+          # Strip git ref prefix from version and use it as suffix for version
+          VERSION=$(echo "${{ github.ref }}" | sed -e 's,.*/\(.*\),\1,')
+
+          # For pull requests just extract the PR number
+          PR_NUMBER=""
+          [ "${{ github.event_name }}" == "pull_request" ] && VERSION=$(echo "${{ github.ref }}" | sed -e 's,.*/\(.*\)/merge,\1,')
+          [ "${{ github.event_name }}" == "pull_request" ] && PR_NUMBER=$VERSION
+
+          # Append version
+          [ "${{ github.event_name }}" == "pull_request" ] && VERSION=$PATCH_VERSION-$BDATE-$VERSION
+
+          # Strip "v" prefix from tag name if it's a tag
+          # [[ "${{ github.ref }}" == "refs/tags/"* ]] && VERSION=$(echo $VERSION | sed -e 's/^v//')
+
+          # Use Docker `latest` tag convention if it's a master branch build
+          [ "$VERSION" == "master" ] && VERSION=latest
+          [ "$VERSION" == "development" ] && VERSION=development
+          [ "${{ github.event_name }}" == "release" ] && VERSION=release
+
+          # Compose REGISTRY_TAGS variable
+          REGISTRY_TAGS="-t $IMAGE_ID:$VERSION"
+
+          # For master branch also supply an extra tag: <PATCH_VERSION>-latest,<MINOR_VERSION>-latest,<MAJOR_VERSION>-latest,<PATCH_VERSION>-<DATE>-<SHA>
+          [ "$VERSION" == "latest" ] && REGISTRY_TAGS="$REGISTRY_TAGS -t $IMAGE_ID:$PATCH_VERSION-latest -t $IMAGE_ID:$MINOR_VERSION-latest -t $IMAGE_ID:$MAJOR_VERSION-latest -t $IMAGE_ID:$PATCH_VERSION-$BDATE-$(git rev-parse --short HEAD)"
+          [ "$VERSION" == "development" ] && REGISTRY_TAGS="$REGISTRY_TAGS -t $IMAGE_ID:$MAJOR_VERSION-development -t $IMAGE_ID:$PATCH_VERSION-$BDATE-$(git rev-parse --short HEAD)"
+          [ "$VERSION" == "release" ] && REGISTRY_TAGS="$REGISTRY_TAGS -t $IMAGE_ID:$PATCH_VERSION-release -t $IMAGE_ID:$MINOR_VERSION-release -t $IMAGE_ID:$MAJOR_VERSION-release -t $IMAGE_ID:$PATCH_VERSION-$BDATE-$(git rev-parse --short HEAD)"
+
+          echo IMAGE_ID=$IMAGE_ID
+          echo VERSION=$VERSION
+          echo REGISTRY_TAGS=$REGISTRY_TAGS
+          echo headref=${{ github.head_ref }}
+
+          SHA_SHORT=${{ github.sha }}
+          [ "${{ github.event_name }}" == "pull_request" ] && SHA_SHORT=$(echo ${{ github.event.pull_request.head.sha }} | cut -c1-8)
+
+          echo "Final image tag to be pushed:"
+          echo $REGISTRY_TAGS
+          echo "REGISTRY_TAGS=$REGISTRY_TAGS" >> $GITHUB_OUTPUT
+          echo "IMAGE_ID=$IMAGE_ID" >> $GITHUB_OUTPUT
+          echo "REGISTRY_TAGS_VERSION=$VERSION" >> $GITHUB_OUTPUT
+          echo "REGISTRY_TAGS_PR_NUMBER=$PR_NUMBER" >> $GITHUB_OUTPUT
+          echo "SHA_SHORT=$SHA_SHORT" >> $GITHUB_OUTPUT
+
+      - name: Login to GHCR
+        run: echo ${{ secrets.GITHUB_TOKEN }} | docker login -u ${{ github.actor }} --password-stdin ghcr.io
+
+      - name: Docker build
+        run: docker build --no-cache ${{ steps.generate.outputs.REGISTRY_TAGS }} .
+
+      - name: Docker push
+        run: docker push ${{ steps.generate.outputs.IMAGE_ID }} --all-tags

.gitignore

@@ -1,24 +1,26 @@
-.vscode
-.DS_Store
-.env
-/Missions_dev/
-/Missions_rel/
-/documentation
-API/logs/*
-
-node_modules/
-
-/Missions
-/db/
-/config/db/
-/dist/*
-/scripts/ignore
-
-#Nested repo where private backend might reside
-/API/MMGIS-Private-Backend
-#Nested repo where private tools might reside
-/scripts/essence/MMGIS-Private-Tools
-/scripts/pre/toolConfigs.js
-sessions
-
-#tools
+.vscode
+.DS_Store
+.env
+.*project
+/node_modules/
+/API/logs/*
+/Missions/*
+!/Missions/.gitkeep
+/private/api/spice/kernels/*
+
+#Nested repo where private backend might reside
+/API/MMGIS-Private-Backend
+#Nested repo where private tools might reside
+#/src/essence/MMGIS-Private-Tools
+/src/essence/MMGIS-Private-Tools-OFF
+
+/config/pre/toolConfigs.json
+/src/pre/tools.js
+
+/build/*
+/data/*
+*__pycache__
+
+sessions
+
+#tools