Bulk Update of On premise docs (#462)

Restructured & Updated On-premise docs as per the following structure:

src/left-nav-title.json

@@ -682,5 +682,11 @@
   "add-test-cases-for-mobile-web-app": {"/docs/test-cases/manage/add-test-cases-for-mobile-web-app/": "Test Cases (Mobile Web App)" },
   "most-common-issues": { "/docs/troubleshooting/salesforce-testing/most-common-issues/": "Most Common Issues" },
   "developer-mode-for-ios": {"/docs/troubleshooting/mobile-apps/developer-mode-for-ios/": "Developer Mode (iOS 16 & Above)" },
-  "mock-apis": {"/docs/test-cases/create-steps-restapi/mock-apis/": "Mock API Support" }
+  "mock-apis": {"/docs/test-cases/create-steps-restapi/mock-apis/": "Mock API Support" },
+  "testsigma-on-prem-architecture": {"/docs/on-premise-setup/pre-installation/testsigma-on-prem-architecture/": "On-Premise System Architecture" },
+  "prerequisites-and-machine-configurations": {"/docs/on-premise-setup/pre-installation/prerequisites-and-machine-configurations/": "Prerequisites" },
+  "setup": {"/docs/on-premise-setup/installation-process/setup/": "Installation Steps" },
+  "post-installation-checklist": {"/docs/on-premise-setup/post-installation/post-installation-checklist/": "Post-Installation Checklist" },
+  "troubleshooting": {"/docs/on-premise-setup/post-installation/troubleshooting/": "Troubleshooting" },
+  "faqs": {"/docs/on-premise-setup/post-installation/faqs/": "FAQs" }
 }

src/pages/docs/on-premise-setup/smtp-configuration.md → src/pages/docs/configuration/smtp-configuration.md

@@ -1,6 +1,6 @@
 ---
 title: "SMTP Configuration in Testsigma"
-order: 26.6
+order: 19.7
 page_id: "SMTP Configuration Setup"
 metadesc: "This article discusses a step-by-step guide to setup Simple Mail Transfer Protocol (SMTP) to trigger emails from a configured email address."
 noindex: false
@@ -40,24 +40,15 @@ You'll need the following for SMTP Configuration:
 ## **Steps to Configure SMTP in Testsigma**
 
 1. Navigate to **Settings > SMTP Configuration**.
-![SMTP Configuration](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/smtp.png)
-
 
 2. Turn on the **SMTP Configuration** toggle.
-![SMTP Toggle](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/smtp_toggle.png)
-
 
 [[info | **NOTE**:]]
 | You will stop getting emails if you turn off the SMTP Configuration toggle. 
 
-
 3. Select **@own**, and enter all the details.
-![Own](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/SMTP_details.png)
-
 
 4. Click on **Save**.
-![Save](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/Save.png) 
-
 
 [[info | **NOTE**:]]
 |If you select Testsigma, the mails will go with default email. For **@own** configuration, you need to enter the following details:<br>
@@ -97,7 +88,7 @@ Here’s a quick GIF demonstrating how to generate the password.
 
 
 [[info | **NOTE**:]]
-|These steps are specific for generating an app password in a Google account. The process may be different for other email clients/services.
+| These steps are specific for generating an app password in a Google account. The process may be different for other email clients/services.
 
 
 

src/pages/docs/on-premise-setup/installation-process/domain-configuration.md

@@ -0,0 +1,57 @@
+---
+title: "Custom Domain Configuration"
+order: 26.22
+page_id: "Custom Domain Configuration"
+metadesc: "This article discusses how to configure custom domains for Docker setup. Custom domains ensures data security, builds user trust, improves SEO, and presents a professional image"
+noindex: false
+search_keyword: ""
+warning: false
+contextual_links:
+- type: section
+  name: "Contents"
+- type: link
+  name: "Steps to Configure Custom Domains"
+  url: "#steps-to-configure-custom-domains"
+---
+
+---
+
+
+Configuring custom domains for Docker setup ensures data security, builds user trust, improves SEO rankings, and presents a professional and branded image to your customers. If you have the custom domain requirements ready, follow the steps in this article to configure custom domains. 
+
+---
+
+
+## **Steps to Configure Custom Domains** 
+
+1. Request the Docker image with the new domain names from Testgigma using GitHub Actions.
+
+2. Replace the HTTPS certificate in the **testsigma-load-balancer** container. For this, store the public key and private key files on the host machine and specify them as volumes in the **docker-compose file**.
+
+   **For Example:**
+
+   ```yaml
+   version: '3.9'
+   services:
+     testsigma_load_balancer:
+       container_name: testsigma-load-balancer
+       image: testsigmainc/onprem:load-balancer-<CustomDomain>-trial-v120
+       ports:
+         - "443:443"
+       networks:
+         - testsigma-network
+       volumes:
+         - ./data/ts_load_balancer_data:/opt/app/ts_load_balancer_data
+         - /path/to/new/server.crt:/usr/local/apache2/ssl/server.crt
+         - /path/to/new/server.key:/usr/local/apache2/ssl/server.key
+
+
+<br>
+
+- Here, replace ***/path/to/new/server.crt*** with the path to the new ***server.crt*** file on your host machine, and replace ***/path/to/new/server.key*** with the path to the new ***server.key*** file on your host machine.
+
+- When you run ***docker-compose up***, the ***server.crt*** and ***server.key*** files in the container will be replaced with the new files from the host machine.
+
+
+
+---