🚗📍 Vehicle Tracking System

Welcome to the Vehicle Tracking System — a microservices-powered platform for tracking, managing, and evaluating vehicle dispatches in real time with a safety-first approach.

---

🧭 What This Is

This system helps companies:

• Monitor vehicle conditions and movements
• Enforce safety rules for dispatching vehicles
• Keep a history of dispatch activity
• Communicate between services using RabbitMQ or pure WebClient calls
• Retrieve notifications via polling

---

💡 Project Structure

/views                       -> Frontend (React apps: admin + user)
/AuthService                 -> Auth microservice
/VehicleService              -> Vehicle microservice
/DispatchService             -> Dispatch handling microservice
/logging-tracking-service    -> Tracking logs + notifications
/ApiGateway                  -> Gateway routing and config

---

🛠️ Technologies Used

🔧 Backend

• Java 17+
• Spring Boot
• Spring Cloud Gateway
• RabbitMQ (optional — can be replaced with direct WebClient calls)

🎨 Frontend

• React
• TailwindCSS (optional)

⚙️ DevOps

• Docker (multi-stage builds and networking)
• Docker Compose (recommended)
• Single Postgres container hosting multiple databases

---

🚦 Safety Score Rules

Each vehicle is assigned a safety score calculated from part conditions:

Score	Status
>= 63	✅ Eligible for dispatch
< 63	❌ Blocked from dispatch

The Dispatch Service automatically blocks unsafe vehicles from being dispatched.

---

🔄 Notification Flow

• Notifications are retrieved by polling endpoints at intervals.

---

Messaging

• Developers can choose:

  1. RabbitMQ-based events for faster async communication, or
  2. Direct WebClient calls for a simpler setup.

---

⚙️ Running the Backend

The system uses one Postgres container for all databases. An init.sql script creates each database and its user automatically.

---

🐳 Quick Start

1. Create your .env

Copy .env.example and set credentials, ports, and API keys manually.

⚠ Security Warning: Never commit .env to GitHub or any public repo — it contains credentials. Add .env to .gitignore.

---

2. Start everything with Docker Compose

From the root directory:

docker compose up --build

This will start:

• Postgres (with all DBs pre-created)
• MongoDB for logging
• RabbitMQ (optional — only if you configure services to use it)
• All microservices (Auth, Dispatch, Vehicle, Logging)
• API Gateway

---

3. Access UIs

• API Gateway → Port from .env (default 8102)
• Frontend Admin UI → http://localhost:3000
• Frontend User UI → http://localhost:3001

---

🔀 Switching Between RabbitMQ and WebClient

You can change the communication mode between services via the .env file.

Look for the MESSAGE_TYPE variable:

MESSAGE_TYPE=rabbitMq   # use RabbitMQ
MESSAGE_TYPE=webClient  # use WebClient instead

If you don’t want RabbitMQ, just leave it set to webClient — the container can still run, but won’t be used.

---

🌐 Frontend Setup

Frontend lives in /views and:

• Uses the API Gateway for backend access
• Polls backend endpoints for notifications
• Works with RabbitMQ-based or WebClient-based backend communications

---

❤️ Why This Exists

We built this to help logistics and automotive companies:

• Improve fleet safety
• Enforce dispatch policies
• Track vehicle activity
• Provide real-time awareness (polling or RabbitMQ-driven)

---

🔐 License & Ownership

Licensed under the Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International Public License (CC BY-NC-ND 4.0) 🔗 https://creativecommons.org/licenses/by-nc-nd/4.0/

---

⚠ Group Project Note

This was built as part of a final academic group project. Core system design and code by Brightdotdev.

---

🙋 Contact

• 📧 Email: iamtherealbright@gmail.com
• 🐙 GitHub: https://github.com/Brightdotdev
• 💼 LinkedIn: https://www.linkedin.com/in/brightdotdev/

---

💻 Made cause my diplaoma requests it