In the traditional logistics sector, matching loads with available trucks is often a manual, fragmented process involving multiple middlemen. This Multi-Tenant SaaS platform digitizes the entire workflow—from load posting and truck availability to smart matching, digital Bilty generation, and GST invoicing.

It provides a centralized ecosystem for Logistics Companies (Tenants) to manage their customers and drivers with complete data isolation.

• Multi-Tenant Architecture: Complete data isolation between different logistics companies (tenants).
• Role-Based Access Control (RBAC): Dedicated dashboards for Admins, Drivers (Truck Owners), and Customers (Load Owners).
• Smart Matching: Algorithm to match available trucks with loads based on capacity and vehicle type.
• Secure Authentication: JWT-based auth with Access/Refresh token rotation and OTP verification via Twilio & Redis.
• Password Recovery: OTP-based forgot password flow for secure account recovery.
• Digital Documentation: Automated generation of 4-copy Bilty and GST Invoices in PDF format.
• Real-time Status Tracking: Workflow management from 'Assigned' to 'In-Transit' and 'Delivered'.

Frontend:

• React.js (Vite)
• React Router (Routing)
• Axios (API Calls with Interceptors)
• CSS-in-JS (Modern, responsive UI)

Backend:

• Node.js & Express.js
• MongoDB & Mongoose (Database & Modeling)
• Redis (OTP Storage & Rate Limiting)
• Twilio (SMS Gateway)
• PDFKit (Document Generation)

Follow these steps to run the project locally.

git clone https://github.com/your-username/Fleetiva-Roadlines.git
cd Fleetiva-Roadlines

### Prerequisites

- Node.js (v18+)
- MongoDB (Local or Atlas)
- Redis Server (Running on port 6379)
- Twilio Account (for SMS features)

### Installation

1. **Clone the repository:**
   ```bash
   git clone https://github.com/your-username/logistics-transport-system.git
   cd logistics-transport-system

After starting both backend and frontend:

• Open http://localhost:3000 in your browser
• Ensure the frontend loads without errors
• Check backend logs to confirm MongoDB is connected

If the application loads successfully, the setup is complete 🎉

2. Backend Setup:

   cd backend
   npm install

   Create a .env file based on .env.example and fill in your credentials.

   Start the backend:

   npm run dev

3. Frontend Setup:

   cd ../frontend
   npm install

   Start the frontend:

   npm run dev

├── .github/
│   ├── ISSUE_TEMPLATE/ # Bug & Feature templates
│   └── workflows/      # CI/CD Pipeline (GitHub Actions)
├── CONTRIBUTING.md     # Open-source contribution guidelines
├── backend/
│   ├── config/         # Service clients (Redis, Twilio)
│   ├── middleware/     # Auth, Role, and Tenant scoping
│   ├── models/         # Mongoose Schemas
│   ├── routes/         # Modular API endpoints
│   ├── utils/          # PDF Generation logic
│   └── server.js       # Entry point
└── frontend/
    ├── src/
    │   ├── api/        # Axios configuration
    │   ├── components/ # Reusable UI components
    │   ├── pages/      # Role-specific dashboards and forms
    │   └── App.jsx     # Routing and Layout logic

This project includes a GitHub Actions workflow for Continuous Integration. The pipeline automatically:

• Performs security audits on backend dependencies.
• Lints the codebase for consistency.
• Verifies frontend builds.

Contributions are welcome! Please read our CONTRIBUTING.md for details on our code of conduct and the process for submitting pull requests.

This project is licensed under the MIT License.