Create release 1.0.0

.github/workflows/integration.yml

@@ -43,9 +43,13 @@ jobs:
 
     - name: Run linting
       run: |
-        yarn workspace user-service lint
         yarn workspace admin-service lint
+        yarn workspace collaboration-service lint
+        yarn workspace frontend lint
         yarn workspace gateway lint
+        yarn workspace matching-service lint
+        yarn workspace question-service lint
+        yarn workspace user-service lint
 
     - name: Run unit tests
       run: |

.github/workflows/production.yml

@@ -18,6 +18,9 @@ env:
   PRISMA_DATABASE_URL: ${{ secrets.PRISMA_DATABASE_URL_PROD }}
   MONGO_ATLAS_URL: ${{ secrets.MONGO_ATLAS_URL_PROD }}
   NEXT_PUBLIC_FRONTEND_FIREBASE_CONFIG: ${{ secrets.FRONTEND_FIREBASE_CONFIG_PROD }}
+  NEXT_PUBLIC_HTTP_PROXY_GATEWAY_ADDRESS: https://api.codeparty.org/
+  NEXT_PUBLIC_WS_MATCH_PROXY_GATEWAY_ADDRESS: https://wsmatch.codeparty.org
+  NEXT_PUBLIC_WS_COLLABORATION_PROXY_GATEWAY_ADDRESS: https://wscollab.codeparty.org
   TWILIO_ACCOUNT_SID: ${{ secrets.TWILIO_ACCOUNT_SID }}
   TWILIO_API_KEY: ${{ secrets.TWILIO_API_KEY }}
   TWILIO_API_SECRET: ${{ secrets.TWILIO_API_SECRET }}
@@ -27,6 +30,7 @@ jobs:
     name: Setup, Build, Publish, and Deploy
     runs-on: ubuntu-latest
     environment: production
+    if: ${{ github.event.workflow_run.conclusion == 'success' }}
     permissions:
       contents: 'read'
       id-token: 'write'
@@ -116,8 +120,8 @@ jobs:
       # Build the Docker images and push to Google Artifact Repository
       - name: Build and push Docker images
         run: |-
-          chmod u+x ./build-prod-images.sh
-          ./build-prod-images.sh
+          chmod u+x ./build-export-prod-images.sh
+          ./build-export-prod-images.sh
         working-directory: ./deployment
 
       # Deploy the Docker images to the GKE cluster

.gitignore

@@ -4,3 +4,5 @@ node_modules
 .env.firebase_emulators_test
 secrets/
 yarn-error.log
+bash.exe.stackdump
+sh.exe.stackdump

README.md

@@ -4,19 +4,19 @@
 
 Prerequisites for PeerPrep Monorepo:
 
-1.  **Yarn:** Ensure you have the latest version of Yarn installed. Yarn
+1. **Yarn:** Ensure you have the latest version of Yarn installed. Yarn
     Workspaces is available in Yarn v1.0 and later.
-2.  Installation (if not already installed):
+2. Installation (if not already installed):
 
     ```bash
     npm install -g yarn
     ```
 
-3.  **Node.js:** Check each application's documentation for the recommended
+3. **Node.js:** Check each application's documentation for the recommended
     Node.js version.
-4.  **Git (Optional but Recommended):**
-5.  **Docker (If deploying with Docker):**
-6.  **Kubernetes Tools (If deploying with Kubernetes):**
+4. **Git (Optional but Recommended):**
+5. **Docker (If deploying with Docker):**
+6. **Kubernetes Tools (If deploying with Kubernetes):**
 
 ---
 
@@ -52,10 +52,19 @@ your services / frontend.
     MONGO_ATLAS_URL=<redacted>
     FIREBASE_SERVICE_ACCOUNT=<redacted>
     NEXT_PUBLIC_FRONTEND_FIREBASE_CONFIG={"apiKey": <redacted>,"authDomain": <redacted>,"projectId": <redacted>,"storageBucket": <redacted>,"messagingSenderId": <redacted>,"appId": <redacted>}
+    TWILIO_ACCOUNT_SID=<redacted>
+    TWILIO_API_KEY=<redacted>
+    TWILIO_API_SECRET=<redacted>
     ```
 Note: For `NEXT_PUBLIC_FRONTEND_FIREBASE_CONFIG`, the JSON should not have newlines since Next.js may not process it correctly.
+The difference between it and `FIREBASE_SERVICE_ACCOUNT` are shown below:
 
-1. **Installing secret detection hooks:** From the root directory, run:
+| Variable | Purpose |
+| -------- | ------- |
+| FIREBASE_SERVICE_ACCOUNT | For backend verification and administrative tasks |
+| NEXT_PUBLIC_FRONTEND_FIREBASE_CONFIG | For the frontend to connect to Firebase |
+
+2. **Installing secret detection hooks:** From the root directory, run:
     ```bash
     pip install pre-commit
     pre-commit install
@@ -66,7 +75,7 @@ As a tip, if you think a file will eventually store secrets, immediately add it
 it in case you forget later on when you have a lot more files to commit.
 
 
-1. **Installing Dependencies:** From the root directory (`/peerprep`), run:
+3. **Installing Dependencies:** From the root directory (`/peerprep`), run:
 
    ```bash
    yarn install
@@ -83,27 +92,27 @@ it in case you forget later on when you have a lot more files to commit.
    This command will install dependencies for all services and the frontend in a
    centralized `node_modules` directory at the root.
 
-1. **Adding Dependencies:** To add a dependency to a specific workspace (e.g.,
+4. **Adding Dependencies:** To add a dependency to a specific workspace (e.g.,
    `user-service`), use:
 
    ```bash
    yarn workspace user-service add [dependency-name]
    ```
 
-1. **Initializing Prisma:** In the root file, run the following:
+5. **Initializing Prisma:** In the root file, run the following:
 
    ```bash
    yarn prisma generate ## Do this whenever we change the models in schema.prisma
    ```
 
-1. **Running Backend Scripts:** To run a script specific to a workspace (e.g.,
+6. **Running Backend Scripts:** To run a script specific to a workspace (e.g.,
    the `start` script for `user-service`), use:
 
    ```bash
    yarn workspace user-service start
    ```
 
-1. **Running Frontend Scripts:** To run the frontend cod, use:
+7. **Running Frontend Scripts:** To run the frontend cod, use:
 
    ```bash
    yarn workspace frontend dev ## For development
@@ -113,25 +122,53 @@ it in case you forget later on when you have a lot more files to commit.
    yarn workspace frontend build ## For first time setup run the build command
    yarn workspace frontend start ## For subsequent runs
    ```
+8. **Running everything at once:** To run everything at once and still maintain the ability to hot-reload your changes, use:
+
+    ```bash
+    ./start-app-no-docker.sh # on mac /linus
+
+    # You can also use the above command on Windows with Git Bash
+
+    ```
 
 ### Getting Started - Docker:
+Docker and Docker Compose are used to set up a simulated production build (meaning that the Docker images and 
+containers that will be spun up locally are almost identical to those in the production environment, with the exception
+of some environment variables).
 
-1. **Run the start-app.sh script:** From the root repo, run
+1. **Run yarn docker:build:** From the root repo, run
 
 ```bash
-./start-app.sh # on mac / linus
+yarn docker:build 
+```
+This will create new Docker images.
 
-# or
+2. **Run yarn docker:devup:** From the root repo, run
+```bash
+yarn docker:devup 
+```
+This will start all the containers.
 
-start-app.sh # on windows
+3. **Once done, run yarn docker:devdown:** From the root repo, run
+```bash
+yarn docker:devdown 
 ```
+This will stop and delete all the containers.
 
-2. Made a change in code? To refresh containers, run
+#### If you want to do all the above steps at once, see the below section
+
+**Run the start-app-with-docker.sh script:** From the root repo, run
 
 ```bash
-docker-compose up --force-recreate --build -d
-docker image prune -f
+./start-app-with-docker.sh # on mac / linus
+
+# You can also use the above command on Windows with Git Bash
 ```
+This will create new Docker images everytime it is run. Be careful of how much disk space you have left.
+
+Any edits you make to the source code will not be automatically reflected on the site. We recommend using Docker
+Compose to check if your changes are likely to work on the production environment once they have been proven to work
+in your local development environment.
 
 ### Notes:
 

deployment/build-prod-images.sh → deployment/build-export-prod-images.sh

@@ -11,13 +11,16 @@ service_array=("admin-service" "collaboration-service" "gateway" "matching-servi
 for i in ${!service_array[@]}; do
   docker build \
     --tag $GKE_REGION-docker.pkg.dev/$PROJECT_ID/$ARTIFACT_REPOSITORY_NAME/${service_array[$i]}:latest \
-    --file prod-dockerfiles/Dockerfile.${service_array[$i]}-prod ..
+    --file prod-dockerfiles/Dockerfile.${service_array[$i]} ..
   docker push $GKE_REGION-docker.pkg.dev/$PROJECT_ID/$ARTIFACT_REPOSITORY_NAME/${service_array[$i]}:latest
 done
 
 # Build and publish frontend prod image
 docker build \
   --build-arg="NEXT_PUBLIC_FRONTEND_FIREBASE_CONFIG_ARG=$NEXT_PUBLIC_FRONTEND_FIREBASE_CONFIG" \
+  --build-arg="NEXT_PUBLIC_HTTP_PROXY_GATEWAY_ADDRESS_ARG=$NEXT_PUBLIC_HTTP_PROXY_GATEWAY_ADDRESS" \
+  --build-arg="NEXT_PUBLIC_WS_MATCH_PROXY_GATEWAY_ADDRESS_ARG=$NEXT_PUBLIC_WS_MATCH_PROXY_GATEWAY_ADDRESS" \
+  --build-arg="NEXT_PUBLIC_WS_COLLABORATION_PROXY_GATEWAY_ADDRESS_ARG=$NEXT_PUBLIC_WS_COLLABORATION_PROXY_GATEWAY_ADDRESS" \
   --tag $GKE_REGION-docker.pkg.dev/$PROJECT_ID/$ARTIFACT_REPOSITORY_NAME/frontend:latest \
-  --file prod-dockerfiles/Dockerfile.frontend-prod ..
+  --file prod-dockerfiles/Dockerfile.frontend ..
 docker push $GKE_REGION-docker.pkg.dev/$PROJECT_ID/$ARTIFACT_REPOSITORY_NAME/frontend:latest

deployment/gke-prod-manifests/collaboration-service-deployment.yaml

@@ -19,6 +19,8 @@ spec:
     spec:
       containers:
         - env:
+            - name: FRONTEND_ADDRESS
+              value: "https://www.codeparty.org"
             - name: PRISMA_DATABASE_URL
               valueFrom:
                 secretKeyRef:

deployment/gke-prod-manifests/matching-service-deployment.yaml

@@ -19,6 +19,10 @@ spec:
     spec:
       containers:
         - env:
+            - name: FRONTEND_ADDRESS
+              value: "https://www.codeparty.org"
+            - name: QUESTION_SERVICE_HOSTNAME
+              value: "question-service"
             - name: PRISMA_DATABASE_URL
               valueFrom:
                 secretKeyRef: