How hctynch/trackhounds works
Major Components
• Frontend Application: Located in the “frontend” directory built using React with Vite. This part comprises the UI views (using multiple components such as Navbar, Home, Add Dogs, Score Entry, etc.), service layers (using Axios to make API calls to the backend), and client-side logic.
• Backend Application: Found under the “trackhounds” directory. It’s a Spring Boot application built according to the MVC (Model-View-Controller) pattern. The structure shows Controllers (like DogController, HuntController, JudgeController), Services (business logic), Repositories (data access), Entities, DTOs, and Exception handling components.
• Infrastructure/Containers: Docker is utilized for both the frontend and backend (as evidenced by the Dockerfiles and docker-compose.yml). Indicate containerized deployment and orchestration via Docker Compose.
• CI/CD Pipelines: GitHub Actions configurations (e.g., backend tests and release workflows) help automate testing and build processes, so include a component showing integration with your version control and continuous integration processes.
Architectural Patterns and Technologies
• Frontend: Highlight that it’s a React application structured with components for major views (e.g., Home, Dogs, Judges, Score Entry, Scratch Sheet, Reports) and service files that manage API requests.
• Backend: Emphasize the layered MVC architecture along with clearly separated concerns — Controllers handle HTTP requests, Services encapsulate business logic, and Repositories manage data persistence with Entities and DTOs defining the domain model.
• Containerization: Note that both frontend and backend are containerized via Docker, and the system is orchestrated with docker-compose.
• Additional Tools: Show supporting technologies like GitHub Actions (for CI/CD), ESLint (for frontend code quality), and Vite (for frontend bundling).