Currently, the Efrei Rugby team relies on a disorganized system for team administration. Attendance for training sessions and events is handled through a messy WhatsApp group using emoji reactions, while event photos are scattered across a public Instagram page. This fragmented approach makes it difficult for coaches to track player commitment and performance over time. My proposed cloud project aims to solve this by building a centralized, custom web platform specifically designed for our rugby team. The application will feature a user dashboard where players can securely log in to register for upcoming training sessions, matches, and social events. Crucially, the platform will act as a historical database for player statistics. It will dynamically display a player's tenure, total training sessions attended, match appearances, tries scored, "Player of the Match" awards, disciplinary cards, and individualized match grades assigned by the coach. The site will also feature a dedicated, secure gallery for team photos. From a technical perspective, the application will be built using a JavaScript-based backend stack (Node.js) connected to a MySQL database to handle user authentication and relational data. This environment will be hosted on an Infrastructure as a Service (IaaS) provider. By configuring a Linux server in the cloud, installing the required JS runtime environments, and securing the relational database, this project directly applies the core learning outcomes of server configuration and cloud architecture. While this initial cloud deployment will serve as a functional prototype to demonstrate my server environment capabilities, my ultimate goal is to launch this platform for the Efrei Rugby team to use in real life next season, with plans to continuously upgrade the architecture and feature set.
For this project, I have chosen a strict Proprietary 'All Rights Reserved' license. Because this platform is being custom-built specifically for my rugby team back home, it will eventually handle sensitive player data, internal team statistics, and private event photos. Therefore, it is important that the intellectual property remains closed-source to prevent unauthorized cloning or distribution of our team's private platform. By retaining full copyright, I ensure that the software and its specific implementation remain exclusively under the control and ownership of the team.