wip

src/content/docs/service-architecture-intelligence/github-integrations/github-cloud-integration.mdx

@@ -1,5 +1,5 @@
 ---
-title: Service Architecture Intelligence with GitHub Cloud Integration
+title: Service Architecture Intelligence with GitHub cloud integration
 tags:
     - New Relic integrations
     - GitHub integration

src/content/docs/service-architecture-intelligence/github-integrations/github-enterprise-integration.mdx

@@ -1,5 +1,5 @@
 ---
-title: Service Architecture Intelligence with GitHub Enterprise Integration
+title: Service Architecture Intelligence with GitHub Enterprise (On-prem)
 tags:
   - New Relic integrations
   - GitHub Enterprise integration
@@ -21,7 +21,6 @@ This integration streamlines the onboarding process for users and teams, simplif
 **Prerequisites**
 
 * Login to your GitHub Enterprise account you plan to integrate with New Relic.
-* You must be the Organization Manager or Authentication Domain Manager.
 * Docker environment to run the collector service within your GHE network.
 
 **To set up the GitHub Enterprise integration:**
@@ -40,7 +39,7 @@ This integration streamlines the onboarding process for users and teams, simplif
         <tr>
           <th>Variable</th>
           <th>Source</th>
-          <th>How to Obtain</th>
+          <th>How to obtain</th>
         </tr>
       </thead>
       <tbody>
@@ -77,15 +76,55 @@ This integration streamlines the onboarding process for users and teams, simplif
       </tbody>
     </table>
 
+    The following are optional environment variables for making API HTTPS.
+
+    <table>
+      <thead>
+        <tr>
+          <th>Optional Variable</th>
+          <th>Source</th>
+          <th>How to obtain</th>
+        </tr>
+      </thead>
+      <tbody>
+        <tr>
+          <td>`SERVER_SSL_KEY_STORE`</td>
+          <td>SSL Configuration</td>
+          <td>Path to the SSL keystore file for HTTPS configuration.</td>
+        </tr>
+        <tr>
+          <td>`SERVER_SSL_KEY_STORE_PASSWORD`</td>
+          <td>SSL Configuration</td>
+          <td>Password for the SSL keystore file.</td>
+        </tr>
+        <tr>
+          <td>`SERVER_SSL_KEY_STORE_TYPE`</td>
+          <td>SSL Configuration</td>
+          <td>Type of the SSL keystore (e.g., PKCS12, JKS).</td>
+        </tr>
+        <tr>
+          <td>`SERVER_SSL_KEY_ALIAS`</td>
+          <td>SSL Configuration</td>
+          <td>Alias for the SSL key within the keystore.</td>
+        </tr>
+        <tr>
+          <td>`SERVER_PORT`</td>
+          <td>SSL Configuration</td>
+          <td>Server port for HTTPS communication. Use 8443 for HTTPS.</td>
+        </tr>
+      </tbody>
+    </table>
+
 3. **Deploy the collector service**: The collector service is delivered as a Docker image. Deployment can be done in one of two ways:
 
     **Option A: Using Docker Compose (Recommended)**
 
     We will provide a sample Docker Compose file that automates the download and deployment of the service.
 
-    1. Download the provided Docker Compose file.
-    2. Configure the environment variables from step 2.
-    3. Run the following command:
+    a. Download the provided Docker Compose file.
+    b. Configure the environment variables as described in step 2.
+    c. Run the following command:
+
        ```bash
        docker-compose up -d
        ```