chore: Integrated SSL configuration for HTTPS into environment config…

README.md

@@ -203,7 +203,7 @@ Here are the steps:
 2. Run `mkcert -install` to install the generated certificate in your trust store. After installed, restart your browser. 
 3. Now you can start the development session as follows:
     ```zsh
-    HTTPS=true SSL_CRT_FILE=localhost.pem SSL_KEY_FILE=localhost-key.pem npm start
+    HTTPS=true npm start
     ```
 4. Open https://localhost:3000/ to view your development session rendered to the browser.
 
@@ -221,6 +221,11 @@ Similarly, some local environment variables must be specified in order to ensure
 - Use `npm run local` to develop locally **without** authentication enabled
 - Use `npm start` to develop locally **with** authentication
     - If environment variables are not configured, you will be prompted to provide them
+    - Provide the `pem` files as follows when configuring the environment variables:
+        ```zsh
+         SSL_CRT_FILE=localhost.pem 
+         SSL_KEY_FILE=localhost-key.pem
+        ```
 
 ## 🎉Acknowledgements 
 Many thanks to the [UMass Lowell Cloud Computing Club](https://umasslowellclubs.campuslabs.com/engage/organization/cloudcomputingclub) members, our faculty advisor [Dr. Johannes Weis](https://www.uml.edu/sciences/computer-science/people/weis-johannes.aspx), and the [UMass Lowell Computer Science Department](https://www.uml.edu/Sciences/computer-science/) for their support and guidance.

env_config/.gt/dev.gt

@@ -9,3 +9,5 @@ AUTHORITY
 CLIENT_ID
 REDIRECT_URI
 SCOPE
+SSL_CRT_FILE
+SSL_KEY_FILE

env_config/configure_dev.sh

@@ -33,6 +33,9 @@ if [ -f "$env_file" ]; then
 else
   # If the file does not exist, prompt for and create it
   . ./env_config/process_gt.sh "$gt_file" "$env_file"
+
+  # Then validate immediately
+  . ./env_config/validate_vars.sh "$gt_file" "$env_file"
 fi
 
 set -a