How raphy/epitechdj works
Project type and purpose
• This is a full-stack, monolithic web application built on Symfony (PHP).
• It clones the core functionality of Plug.DJ (“EpitechDJ”) for Epitech students: user authentication via Epitech, video queuing, voting, and playback.
File structure
• Top-level Symfony structure:
• app/ – configuration (config.yml, routing.yml, security.yml), cache, logs, kernel, console, autoload
• src/ – application code broken into Bundles
• AppBundle – controllers (Authentication, Home, Player, Video, Vote), Entities (Video, Vote), Twig views, public assets (CSS/JS/images)
• RaphyEpitechUserBundle – reusable bundle handling Epitech OAuth, User entity, custom security providers
• web/ – document root: app.php, app_dev.php, static assets, config.php
• composer.json/lock – dependencies
• PHPUnit config – tests likely under app/phpunit.xml.dist
• Patterns & choices: MVC (Controllers → Views → Entities via Doctrine ORM), Dependency Injection (services.yml), Bundles for modularity.
README for additional insights
• Confirms it’s a Plug.DJ-style video-voting web app.
Detail without overcomplicating
• Don’t forget to show asset flow: Client requests CSS/JS → web/Resources/public.