How sashi-u/juice-shop works
Project type and purpose
• This is a full‑stack, intentionally vulnerable web application (“OWASP Juice Shop”) built for security training, CTFs and demonstration of common web vulnerabilities.
• The README confirms it’s a Node.js/Express backend serving a single‑page Angular front end, with persistence in MongoDB (and optional SQLite for packaged distributions), plus additional services (e.g. FTP folder, file uploads, JWT key server, socket.io notifications).
File structure
• Top‑level:
• app.js / server.js – entry points
• config/ – environment‑specific YAML settings
• data/ – data layer (Mongo connector, static data, caching)
• frontend/ – Angular workspace (src/app components, services, assets, environments, build configs)
• routes/ – Express route handlers (REST API endpoints, file server, key server, OAuth, 2FA, etc.)
• models/ – Mongoose schema definitions
• lib/ – startup routines, utilities, security validators, custom middleware
• views/ – server‑side Jade templates for optional pages (e.g. userProfile, themes)
• test/ – unit/integration tests (Mocha/Chai for API, Protractor e2e)
• Dockerfile, Vagrant scripts, CI configs – deployment artifacts
• swagger.yml – API documentation
README for additional insights
• Confirms use cases: deploy on Heroku, Docker, Vagrant, EC2, Azure.
• Mentions configuration via YAML files in /config.
• Points to architecture overview on the project site (but we’ll reverse‑engineer from file tree).
Detailed coverage
• Swagger documentation component and testing pipelines (optional CI logos).
• Config injection: config/*.yml → Express Startup.
• Don’t forget the key external services (Heroku, Docker Hub).