Campus 2.0 – Multi-Portal LMS on OVH Cloud

Campus 2.0 is a large-scale Learning Management System consisting of multiple portals (Student, Teacher, Admin, and UAA) built on a microservices architecture. The challenge was to deploy a complex multi-service system in production with secure networking, persistent data handling, real-time communication tools, and full observability while ensuring stability and zero-downtime operations.

Objective

To design and deploy a fully production-ready, containerized LMS platform on an OVH dedicated server with secure reverse proxy routing, multi-service architecture, persistent storage, automated SSL, and a complete monitoring and logging stack.

Architecture Overview

The system was deployed using Docker Compose on an OVH dedicated server. Multiple React frontends (Student, Teacher, Admin dashboards) were connected to Node.js microservices (cloud-school, cloud-uaa) with MongoDB replica set for data persistence and Redis for caching. Traefik was used as a reverse proxy with automatic Let’s Encrypt SSL. Persistent storage was configured using host-mounted volumes. A full observability stack (Prometheus, Grafana, Loki, Alloy) provided centralized logging, metrics, and monitoring.

Tools & Technologies Used

Docker, Docker Compose, Traefik, OVH Dedicated Server, MongoDB Replica Set, Redis, Node.js, React, Prometheus, Grafana, Loki, Alloy, GitHub Actions, S3, BigBlueButton (BBB).

Implementation Steps

• Designed multi-service Docker Compose architecture for all LMS components.
• Configured Traefik as reverse proxy with automatic SSL.
• Set up MongoDB replica set for high availability and data consistency.
• Implemented persistent storage using host-mounted volumes for uploads.
• Configured explicit Docker networking for inter-service communication.
• Integrated Redis caching layer for performance optimization.
• Deployed BigBlueButton for real-time virtual classroom integration.
• Implemented full observability stack using Prometheus, Grafana, Loki, and Alloy.
• Ensure Databases backup via scripting on cloud.
• Enabled zero-downtime redeployments for continuous updates via Github Actions.

Challenges Faced

• File uploads not persisting after container restarts.
• SSL certificate issuance failures due to ACME rate limits and ALPN issues.
• Inter-service communication failures due to network misconfiguration.
• Lack of centralized logs and system observability.

Troubleshooting & Solutions

Resolved persistent storage issues by implementing correct host-mounted volumes with proper ownership (UID/GID mapping). Fixed SSL issues by switching to HTTP-01 challenge and resetting ACME storage. Solved networking issues by explicitly defining Docker networks for all services. Implemented full observability stack (Loki + Prometheus + Grafana + Alloy) to centralize logs, metrics, and alerts for system-wide visibility.

Key Learnings

This project strengthened expertise in multi-service architecture, production-grade DevOps design, container orchestration, observability engineering, and solving real-world infrastructure challenges at scale.

Live Project Screenshots