How luisegui/dunktomic works
Project Type and Purpose
• Dunktomic is a full-stack sports reservation platform.
• Frontend: Vue 3 + Vite single-page app for user interaction.
• Backend: Spring Boot multi-module Java application implementing REST API, layered with Domain-Driven Design (DDD) / hexagonal principles.
• Infrastructure services: MySQL database, Keycloak for authentication, Docker Compose to orchestrate backend + DB + Keycloak.
File Structure
• Top‐level directories:
• frontend – Vue code, assets, components, pages, services (HTTP, API, local storage) and its Dockerfile.
• backend – Multi-module Maven project under backend/code:
– boot: Spring Boot launcher + configuration (CORS, security, logging, Keycloak client).
– api/rest: Controllers and DTOs exposing HTTP endpoints (AuthController, ClubsController, PlayersController).
– application: Use case implementations and application-level DTOs.
– domain: Core entities, value objects, repository interfaces, domain exceptions.
– infrastructure:
• database: JPA/Hibernate adapters & entities mapping to MySQL.
• repository: adapters mapping domain repositories to external data stores.
• keycloak-client: REST client against Keycloak’s OpenAPI.
• db/mysql/dev: Dockerfile, init scripts for MySQL.
• keycloak: Dockerfile, realm configuration, setup script.
• scripts: Python script + JSON data for populating clubs via API.
• docker-compose.yml: orchestrates backend (built via backend/deployment), db, Keycloak.
README
• Describes functional requirements (search/book courts, manage matches, chat, community).
• Non-functional stack: Spring, Vue, Docker, GitHub Actions.
• Deployment via Docker Compose (backend, DB, Keycloak) + separate npm dev server for frontend.
Detail
• Maven module as a sub-component in the backend block
• How DTOs flow from Controllers down to Use Cases and back
• Where exceptions are handled (RestExceptionHandler in API layer)