How kucharze-kodu/gamegatherapi works
Project type and purpose
• This is a backend‐only web application (GameGather) exposing a RESTful API to support a board‐game management frontend (not included in the repo).
• Purpose: allow users to register/login, manage collections, create/join gaming sessions, track stats, and send email notifications.
File structure
• Four logical layers under src/:
• GameGather.Api – the HTTP entry point, minimal API modules (Authentication, PlayerManager, SessionGame).
• GameGather.Application – CQRS command/query definitions, handlers, validators, domain events, dependency‐injection setup.
• GameGather.Domain – Aggregate roots, value objects, domain events and errors.
• GameGather.Infrastructure – EF Core DbContext & migrations, repository implementations, unit‐of‐work, authentication (JWT provider), outbox pattern & background job, email service, configuration.
• Deployment artifacts: Dockerfile in Api, docker-compose.yml, Terraform scripts to provision PostgreSQL and other infrastructure.
README for additional insights
• Core technologies: ASP.NET Core 8; EF Core 8; PostgreSQL; Docker; REST API; Swagger.
• Patterns: CQRS, Repository, Unit of Work, Dependency Injection, MediatR.