How rollingcodeschool/api_rest_web24 works
This is an in-development Express ecommerce API whose implemented workflow is basic account access: clients reach authentication routes, which list users, register an account, or begin login. Registration generates a verification code, saves a user, and attempts to send email; login currently stops after retrieving the user. MongoDB is configured at startup. The README’s route table differs from the route implementation, and its claim that email is undeveloped conflicts with the sampled mail-sending code; verification itself is not implemented.
Main entry points: auth.routes.js Auth routes · index.js Express app · auth.controller.js Register user · User.js User model
Components 11
API runtime
- Express app
index.js - Auth routes
src/routes/auth.routes.js
User accounts
- List users
src/controllers/auth.controller.js - Register user
src/controllers/auth.controller.js - Login attempt
src/controllers/auth.controller.js - User model
src/models/User.js
External services
- Database connector
src/config/database.js - MongoDB
- Verification mailer
src/config/nodemailer.js - SMTP service
Other components
- API client
Connections 12
- API client → Express app: sends requests
README.md - Express app → Auth routes: mounts routes
index.js - Express app → Database connector: connects database
index.js - Database connector → MongoDB: connects to
src/config/database.js - Auth routes → List users: dispatches GET
src/routes/auth.routes.js - Auth routes → Register user: dispatches POST
src/routes/auth.routes.js - Auth routes → Login attempt: dispatches POST
src/routes/auth.routes.js - List users → User model: queries users
src/controllers/auth.controller.js - Register user → User model: creates and saves
src/controllers/auth.controller.js - Login attempt → User model: looks up user
src/controllers/auth.controller.js - Register user → Verification mailer: sends verification
src/controllers/auth.controller.js - Verification mailer → SMTP service: sends email
src/config/nodemailer.js