How codeurjc-students/2025-mymlb works
Project type and purpose
• This is a full-stack web application (“MyMLB Portal”) for displaying MLB information, managing user accounts, ticket purchases, and administrative operations.
• Frontend: Angular SPA providing responsive UI and charts.
• Backend: Spring Boot REST API handling business logic, security, data access, and static asset hosting.
• Database: MySQL storing users, teams, games, tickets, and related entities.
• CI/CD: GitHub Actions + Docker + Sonar for build, test, analysis, and deployments.
• External services: Email delivery for notifications and password recovery.
File structure
• Top-level folders:
• .github/workflows: CI pipelines for basic and full builds, Sonar analysis.
• backend: Maven Spring Boot project
– Controllers, Services, Repositories, Models reflect a layered MVC pattern
– application.properties configures database and mail settings
– static directory holds compiled Angular assets (index.html, JS bundles, CSS)
– src/test contains unit, integration, and end-to-end tests using JUnit, Mockito, AssertJ, REST-Assured
• frontend: Angular CLI project
– src/app: Components, Services, Models, routing, styles
– cypress and Karma/Jasmine configs for front-end e2e and unit tests
– proxy.conf.json to forward API calls to backend during development
• Build and packaging:
• Maven wrapper and pom.xml drive backend build
• package.json + Angular CLI drive frontend build
• Dockerfiles (not shown) likely containerize both pieces
Key insights from README
• Client-server architecture over HTTPS
• REST endpoints for user and admin workflows
• Role-based navigation (anonymous, registered, admin)
• Automated standings and statistics computed server-side
• ng2-charts integration for visualization
• Docker used in CI/CD for consistent environment