chore: move proto files into individual services

Author: tituschewxj

apps/matching-service/README.md

@@ -76,20 +76,23 @@ Client sends matching parameters:
   "type": "match_request",
   "topics": ["Algorithms", "Arrays"],
   "difficulties": ["Easy", "Medium"],
-  "username": "Jane Doe"
+  "username": "1f0myn"
 }
 ```
 
 Server response on successful match:
 
 ```json
 {
-  "type": "match_found",
-  "matchId": "1c018916a34c5bee21af0b2670bd6156",
-  "user": "zkb4px",
-  "matchedUser": "JohnDoe",
-  "topic": "Algorithms",
-  "difficulty": "Medium"
+  "type": "match_question_found",
+  "match_id": "c377f463d380a9bd1dd03242892ef32e",
+  "user": "1f0myn",
+  "matched_user": "jrsznp",
+  "matched_topics": ["Graphs", "Bit Manipulation", "Databases"],
+  "question_doc_ref_id": "5lObMfyyKPgNXSuLcGEm",
+  "question_name": "Repeated DNA Sequences",
+  "question_difficulty": "medium",
+  "question_topics": ["Algorithms", "Bit Manipulation"]
 }
 ```
 
@@ -128,21 +131,25 @@ Before running the following commands, ensure that the URL for the Redis server
 To run the application via Docker, run the following command:
 
 1. Set up the Go Docker container for the matching service
+
 ```bash
 docker build -f Dockerfile -t match-go-app .
 ```
 
 2. Create the Docker network for Redis and Go
+
 ```bash
 docker network create redis-go-network
 ```
 
 3. Start a new Redis container in detached mode using the Redis image from Docker Hub
+
 ```bash
 docker run -d --name redis-container --network redis-go-network redis
 ```
 
 4. Run the Go Docker container for the matching-service
+
 ```bash
 docker run -d -p 8081:8081 --name go-app-container --network redis-go-network match-go-app
 ```

apps/matching-service/go.mod

@@ -2,16 +2,13 @@ module matching-service
 
 go 1.23.1
 
-replace proto => ../proto
-
 require (
 	github.com/bsm/redislock v0.9.4
 	github.com/gorilla/websocket v1.5.3
 	github.com/joho/godotenv v1.5.1
 	github.com/redis/go-redis/v9 v9.6.2
 	google.golang.org/grpc v1.67.1
 	google.golang.org/protobuf v1.35.1
-	proto v0.0.0-00010101000000-000000000000
 )
 
 require (

apps/matching-service/processes/performmatches.go

@@ -8,7 +8,7 @@ import (
 	"log"
 	"matching-service/databases"
 	"matching-service/models"
-	pb "proto/questionmatching"
+	pb "matching-service/proto"
 
 	"matching-service/servers"
 

…/questionmatching/questionmatching.pb.go …ing-service/proto/questionmatching.pb.goapps/proto/questionmatching/questionmatching.pb.go renamed to apps/matching-service/proto/questionmatching.pb.go apps/proto/questionmatching/questionmatching.pb.go renamed to apps/matching-service/proto/questionmatching.pb.go

@@ -2,7 +2,7 @@ package servers
 
 import (
 	"log"
-	pb "proto/questionmatching"
+	pb "matching-service/proto"
 
 	"google.golang.org/grpc"
 	"google.golang.org/grpc/credentials/insecure"

…tionmatching/questionmatching_grpc.pb.go …ervice/proto/questionmatching_grpc.pb.goapps/proto/questionmatching/questionmatching_grpc.pb.go renamed to apps/matching-service/proto/questionmatching_grpc.pb.go apps/proto/questionmatching/questionmatching_grpc.pb.go renamed to apps/matching-service/proto/questionmatching_grpc.pb.go

@@ -36,7 +36,8 @@ export PATH="$PATH:$(go env GOPATH)/bin"
 Now use the protoc compiler to generate the Go code for the service and messages.
 
 ```bash
-protoc --go_out=. --go-grpc_out=. ./questionmatching.proto
+protoc --go_out=../matching-service --go-grpc_out=../matching-service ./questionmatching.proto
+protoc --go_out=../question-service --go-grpc_out=../question-service ./questionmatching.proto
 ```
 
 This command will generate two files:

apps/matching-service/servers/grpc.go

@@ -2,7 +2,7 @@ syntax = "proto3";
 
 package questionmatching;
 
-option go_package = "./questionmatching";
+option go_package = "./proto";
 
 message MatchQuestionRequest {
     repeated string matched_topics = 1;