How momen165/devquest works
Project type and purpose
• DevQuest is a full-stack coding education platform:
• Frontend: React + Vite app providing interactive lessons, code editor, dashboards
• Backend: Node.js + Express REST API handling auth, courses, code execution, payments
• Supporting services: PostgreSQL, AWS S3 storage, Stripe payments, JWT auth
File structure
• Top-level split:
├ client/ → React app (src/components, src/pages, AuthContext, ProtectedRoute, utils, assets)
└ server/ → Express app (config, controllers, routes, middleware, models, migrations, utils)
• Patterns:
• MVC-style on backend (routes → controllers → models)
• Context API + React Router on frontend
• Code execution endpoint likely uses sandboxed service or Docker behind codeExecution.controller
• Config & build scripts:
• client/vite.config.mjs, server/server.js, migration SQL files, dotenv for env vars
README for additional insights
• Technologies: React 18, Context API, Axios, Monaco Editor, Express, PostgreSQL, JWT, AWS S3, Stripe
• Features: interactive editor, multi-language support, progress tracking, admin dashboards
• Security: Helmet, rate limiting, input validation, CORS
Elements
• Labels: e.g., “React App”, “Express API”, “PostgreSQL DB”, “Stripe”, “AWS S3”
• Client → Server (HTTP/HTTPS)
• Server → Database (SQL)
• Server → S3 (S3 API)
• Server → Stripe (REST)
• Server → Code Sandbox (RPC or HTTP)
• Blue rectangles for UI components
• Orange rectangles for backend services
• Red clouds for external services
Detailed capture of essential elements
• File-upload flow: client uploads via React form → multer middleware → S3 utils → AWS S3
• Code execution flow: user code → codeExecution.controller → sandbox → test runner → back
• Payment flow: purchase → payment.controller → Stripe → webhook back to server → update DB
Guidelines for the engineer: