How dsanchos/auto-backend works
This is a NestJS API for user authentication and basic automobile listing management. Clients register or log in to receive a JWT, can retrieve their profile through an authenticated endpoint, and can create or browse automobile records. The map reflects sampled controller and service calls; the README is only a generic NestJS starter and does not document additional product capabilities.
Main entry points: auth.controller.ts Auth endpoints · auth.service.ts Auth service · users.service.ts Users service · main.ts HTTP bootstrap
Components 14
API entry
- HTTP bootstrap
src/main.ts - App composition
src/app.module.ts
Identity
- Auth endpoints
src/modules/auth/auth.controller.ts - Auth service
src/modules/auth/auth.service.ts - JWT provider
src/modules/auth/auth.module.ts - JWT guard
src/modules/auth/jwt-auth.guard.ts - JWT strategy
src/modules/auth/strategy/jwt.strategy.ts - Users service
src/modules/users/users.service.ts
Auto listings
- Auto endpoints
src/modules/auto/auto.controller.ts - Auto service
src/modules/auto/auto.service.ts
Persistence
- User model
src/modules/users/schemas/users.schema.ts - Auto model
src/modules/auto/schemas/auto.schemas.ts - MongoDB
Other components
- API client
Connections 16
- API client → HTTP bootstrap: HTTP requests
- HTTP bootstrap → App composition: creates app
- App composition → MongoDB: connects
- API client → Auth endpoints: auth requests
- Auth endpoints → Auth service: registers or logs in
- Auth service → Users service: creates or finds user
- Auth service → JWT provider: signs token
- Auth endpoints → JWT guard: guards profile
- JWT guard → JWT strategy: validates token
- Auth endpoints → Users service: loads profile
- Users service → User model: queries or saves
- User model → MongoDB: persists users
- API client → Auto endpoints: listing requests
- Auto endpoints → Auto service: creates or queries
- Auto service → Auto model: queries or saves
- Auto model → MongoDB: persists listings