Feedback

.github/workflows/ci.yml

@@ -0,0 +1,34 @@
+name: Run Unit Tests For Modified Services
+
+on:
+  pull_request:
+    types:
+      - opened
+      - reopened
+      - synchronize
+      - ready_for_review
+    paths:
+      - "services/question-service/**"
+
+jobs:
+  question-service-unit-test:
+    runs-on: ubuntu-latest
+
+    defaults:
+      run:
+        working-directory: services/question-service
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v2
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v2
+        with:
+          node-version: 18
+
+      - name: Install dependencies
+        run: npm install
+
+      - name: Run tests
+        run: npm run test

.github/workflows/collaboration-service.yml

@@ -0,0 +1,33 @@
+name: Build and Push Collaboration Service image to GitLab Container Registry
+
+on:
+  workflow_dispatch:
+  push:
+    branches:
+      - master # Adjust this to the branch you want to trigger the workflow on
+    paths:
+      # github workflow will only trigger at the exact path
+      # add "**" at the end of the path so that any changes to sub-directories will be triggered
+      - "services/collaboration-service/**"
+
+jobs:
+  build-and-push:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v2
+
+      - name: Login to GitLab Container Registry
+        run: docker login registry.gitlab.com -u ${{ secrets.GITLAB_USERNAME }} -p ${{ secrets.DOCKER}}
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v1
+
+      - name: Build and push
+        uses: docker/build-push-action@v2
+        with:
+          context: services/collaboration-service
+          file: ./services/collaboration-service/Dockerfile
+          push: true
+          tags: registry.gitlab.com/peerprepgroup51sem1y2023/docker/collaboration-service:latest

.github/workflows/front-end-gke.yml

@@ -0,0 +1,33 @@
+name: Build and Push front-end-gke image to GitLab Container Registry
+
+on:
+  workflow_dispatch:
+  push:
+    branches:
+      - master # Adjust this to the branch you want to trigger the workflow on
+    paths:
+      # github workflow will only trigger at the exact path
+      # add "**" at the end of the path so that any changes to sub-directories will be triggered
+      - "front-end/peer-prep/**"
+
+jobs:
+  build-and-push:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v2
+
+      - name: Login to GitLab Container Registry
+        run: docker login registry.gitlab.com -u ${{ secrets.GITLAB_USERNAME }} -p ${{ secrets.DOCKER}}
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v1
+
+      - name: Build and push
+        uses: docker/build-push-action@v2
+        with:
+          context: front-end/peer-prep
+          file: ./front-end/peer-prep/Dockerfile.gke
+          push: true
+          tags: registry.gitlab.com/peerprepgroup51sem1y2023/docker/frontend-gke:latest

.github/workflows/front-end.yml

@@ -0,0 +1,33 @@
+name: Build and Push front-end image to GitLab Container Registry
+
+on:
+  workflow_dispatch:
+  push:
+    branches:
+      - master # Adjust this to the branch you want to trigger the workflow on
+    paths:
+      # github workflow will only trigger at the exact path
+      # add "**" at the end of the path so that any changes to sub-directories will be triggered
+      - "front-end/peer-prep/**"
+
+jobs:
+  build-and-push:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v2
+
+      - name: Login to GitLab Container Registry
+        run: docker login registry.gitlab.com -u ${{ secrets.GITLAB_USERNAME }} -p ${{ secrets.DOCKER}}
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v1
+
+      - name: Build and push
+        uses: docker/build-push-action@v2
+        with:
+          context: front-end/peer-prep
+          file: ./front-end/peer-prep/Dockerfile.prod
+          push: true
+          tags: registry.gitlab.com/peerprepgroup51sem1y2023/docker/frontend:latest

.github/workflows/matching-service.yml

@@ -0,0 +1,33 @@
+name: Build and Push matching-service APIs image to GitLab Container Registry
+
+on:
+  workflow_dispatch:
+  push:
+    branches:
+      - master # Adjust this to the branch you want to trigger the workflow on
+    paths:
+      # github workflow will only trigger at the exact path
+      # add "**" at the end of the path so that any changes to sub-directories will be triggered
+      - "services/matching-service/**"
+
+jobs:
+  build-and-push:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v2
+
+      - name: Login to GitLab Container Registry
+        run: docker login registry.gitlab.com -u ${{ secrets.GITLAB_USERNAME }} -p ${{ secrets.DOCKER}}
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v1
+
+      - name: Build and push
+        uses: docker/build-push-action@v2
+        with:
+          context: services/matching-service
+          file: ./services/matching-service/Dockerfile
+          push: true
+          tags: registry.gitlab.com/peerprepgroup51sem1y2023/docker/matching-service:latest

.github/workflows/matching-worker-service.yml

@@ -0,0 +1,33 @@
+name: Build and Push matching-worker-service image to GitLab Container Registry
+
+on:
+  workflow_dispatch:
+  push:
+    branches:
+      - master # Adjust this to the branch you want to trigger the workflow on
+    paths:
+      # github workflow will only trigger at the exact path
+      # add "**" at the end of the path so that any changes to sub-directories will be triggered
+      - "services/matching-worker-service/**"
+
+jobs:
+  build-and-push:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v2
+
+      - name: Login to GitLab Container Registry
+        run: docker login registry.gitlab.com -u ${{ secrets.GITLAB_USERNAME }} -p ${{ secrets.DOCKER}}
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v1
+
+      - name: Build and push
+        uses: docker/build-push-action@v2
+        with:
+          context: services/matching-worker-service
+          file: ./services/matching-worker-service/Dockerfile
+          push: true
+          tags: registry.gitlab.com/peerprepgroup51sem1y2023/docker/matching-worker-service:latest

.github/workflows/profile-service.yml

@@ -0,0 +1,33 @@
+name: Build and Push profile-service APIs image to GitLab Container Registry
+
+on:
+  workflow_dispatch:
+  push:
+    branches:
+      - master # Adjust this to the branch you want to trigger the workflow on
+    paths:
+      # github workflow will only trigger at the exact path
+      # add "**" at the end of the path so that any changes to sub-directories will be triggered
+      - "services/profile-service/**"
+
+jobs:
+  build-and-push:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v2
+
+      - name: Login to GitLab Container Registry
+        run: docker login registry.gitlab.com -u ${{ secrets.GITLAB_USERNAME }} -p ${{ secrets.DOCKER}}
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v1
+
+      - name: Build and push
+        uses: docker/build-push-action@v2
+        with:
+          context: services/profile-service
+          file: ./services/profile-service/Dockerfile
+          push: true
+          tags: registry.gitlab.com/peerprepgroup51sem1y2023/docker/profile-service:latest

.github/workflows/question-service.yml

@@ -0,0 +1,33 @@
+name: Build and Push Question Service to Gitlab Container Registry
+
+on:
+  push:
+    branches:
+      - master # Adjust this to the branch you want to trigger the workflow on
+    paths:
+      - "services/question-service/**"
+  workflow_run:
+    workflows: ["ci.yml"] # Name of the CI workflow
+    types:
+      - completed
+jobs:
+  build-and-push:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v2
+
+      - name: Login to GitLab Container Registry
+        run: docker login registry.gitlab.com -u ${{ secrets.GITLAB_USERNAME }} -p ${{ secrets.DOCKER }}
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v1
+
+      - name: Build and push
+        uses: docker/build-push-action@v2
+        with:
+          context: services/question-service
+          file: ./services/question-service/Dockerfile
+          push: true
+          tags: registry.gitlab.com/peerprepgroup51sem1y2023/docker/question-service:latest

.gitignore

@@ -0,0 +1,2 @@
+
+*.exe

.vscode/settings.json

@@ -0,0 +1,13 @@
+{
+  "editor.formatOnSave": true,
+  "[typescript]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  },
+  "[json]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  },
+  "[dockerfile]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  },
+  "files.insertFinalNewline": true
+}

README.md

@@ -1 +1,90 @@
-# AssignmentTemplate
+[![Review Assignment Due Date](https://classroom.github.com/assets/deadline-readme-button-24ddc0f5d75046c5622901739e7c5dd533143b0c8e959d652212380cedb1ea36.svg)](https://classroom.github.com/a/6BOvYMwN)
+# Welcome to CS3219 Group 51's Peer Prep app!
+
+<p align="center">
+<img src="./images/Peer Prep Logo.png" align="center" height=auto width="300">
+</p>
+
+Welcome to Peer Prep, your ultimate destination for collaborative learning and problem-solving! At Peer Prep, we've created a dynamic web application designed to empower users to come together, discuss curated questions, and enhance their problem-solving skills. With our innovative features, you can seamlessly collaborate with peers, engage in real-time discussions through our integrated chat feature, and even visualize code as you tackle challenges together. We take the guesswork out of finding the right study partner by matching you with individuals who share your interest and are at a similar difficulty level. Our interactive platform ensures that learning is not only effective but also enjoyable. Join us on this exciting journey to elevate your skills, anytime and anywhere at Peer Prep!
+
+## Features
+
+🔒 Authenticate with email/password, Google, Twitter & Github
+
+👀 View questions curated by our team
+
+💬 Chat with other users
+
+💻 Collaborate with other users with a live code-editor
+
+🔗 Match with other users based on question difficulty
+
+✍️ Customize personal profile
+
+`*` refers to ongoing development!
+
+## Tech Stack
+
+**Client:** React, Redux Toolkit, React Router v6, Axios, MaterialUI
+
+**Animations:** Lottiefiles
+
+**Server:** Node, Express
+
+**Containerization:** Docker, Docker Compose
+
+**Cloud:** Google Cloud
+
+**Authentication:** Google Firebase SSO
+
+**Databases:** MongoDB, PostgreSQL
+
+**Message Broker:** RabbitMQ
+
+**API Gateway:** NGINX Proxy Manager
+
+**DNS Server:** GoDaddy
+
+**CI/CD Tools:** Watchtower, Github Actions
+
+## Notable Links
+
+[1. Peer Prep Web App](https://app.peerprepgroup51sem1y2023.xyz)
+
+[2. Trello Kanban Board](https://trello.com/b/Cln8WZMI/cs3219-group-51-kanban)
+
+[3. Figma Wireframes](https://www.figma.com/file/KH7a2ZONAF1fZEdaRzTcm1/PeerPrep-Full-Wireframe?type=design&node-id=0%3A1&mode=design&t=siju64nLq9VpRDgM-1)
+
+## Run Locally
+
+### Prerequisites:
+
+1. Git
+2. Docker or Docker Desktop
+3. Web browser of your choice (best supported on Chromium)
+
+### Steps:
+
+Clone the project
+
+```bash
+  git clone https://github.com/CS3219-AY2324S1/ay2324s1-course-assessment-g51.git
+```
+
+Go to Server-Configs
+
+```bash
+  cd ~/ay2324s1-course-assessment-g51/Server-Configs/Without-k8/dev
+```
+
+Deploy all containers
+
+```bash
+  docker compose up -d
+```
+
+Access Peer Prep
+
+```bash
+  http://localhost:3000
+```