How patrick-1810/matchfit-backend works
MatchFit Backend is currently a minimal NestJS API shell: the documented user-facing workflow is an HTTP client reaching the API, which boots the application and registers a shared Redis cache. The tree does not contain the README’s illustrative auth, users, matches, chat, or events modules, nor an application-level Prisma data-access layer; those capabilities cannot be mapped as implemented. PostgreSQL/Prisma setup is documented, but no runtime connection from the API is evidenced in the sampled source.
Main entry points: main.ts API bootstrap · app.module.ts App module · cache.module.ts Redis cache module
Components 5
API runtime
- API bootstrap
src/main.ts - App module
src/app.module.ts
Cache integration
- Redis cache module
src/infrastructure/cache/cache.module.ts
Other components
- HTTP client
- Redis
Connections 4
- HTTP client → API bootstrap: sends HTTP
README.md - API bootstrap → App module: boots
src/main.ts - App module → Redis cache module: imports
src/app.module.ts - Redis cache module → Redis: connects to
src/infrastructure/cache/cache.module.ts