How m1cckey/secure-shop works
secure-shop is a small Django demo site described as being for attack detection. Its visible request path is access-logging middleware, URL routing, page handlers, and rendered templates. The excerpts show page rendering and access-log writes, but no attack-detection logic, authentication processing, or search implementation; those paths should not be inferred from page names. The graph focuses on the evidenced runtime and configured request flow.
Main entry points: middleware.py Access middleware · settings.py Django settings · web/urls.py Project routes · shop/urls.py Shop routes
Components 9
Request handling
- Access middleware
web/shop/middleware.py - Access log
- Project routes
web/web/urls.py - Shop routes
web/shop/urls.py
Site pages
- Page handlers
web/shop/views.py - Page templates
web/templates
Runtime configuration
- Django settings
web/web/settings.py - Jinja environment
web/shop/jinja2env.py
Other components
- Visitor
Connections 9
- Visitor → Access middleware: sends request
- Access middleware → Access log: writes access entry
web/shop/middleware.py - Access middleware → Project routes: passes request
web/shop/middleware.py - Project routes → Shop routes: includes routes
web/web/urls.py - Shop routes → Page handlers: dispatches routes
web/shop/urls.py - Page handlers → Page templates: renders pages
web/shop/views.py - Django settings → Access middleware: configures middleware
web/web/settings.py - Django settings → Project routes: selects routes
web/web/settings.py - Django settings → Jinja environment: sets environment
web/web/settings.py