How raconer/django-practice works
This is a small Django practice project with one implemented API workflow: a GET request is routed to a content view that returns a success JSON response. The project also configures SQLite and custom 404/DRF exception handling, and exposes WSGI and ASGI server entry points. The README describes a basic Django project but does not document additional product capabilities; the graph therefore reflects only the visible runtime. Framework internals are external, and no database access by the content view is shown.
Main entry points: config/urls.py Root routes · settings.py Django settings · content/urls.py Content routes · views.py Content view
Components 11
Request routing
- Root routes
config/urls.py - Content routes
apps/content/urls.py - Content view
apps/content/views.py
Django runtime
- JSON response
apps/content/views.py - Django settings
config/settings.py - SQLite database
db.sqlite3 - WSGI entry
config/wsgi.py - ASGI entry
config/asgi.py
Error handling
- Custom exceptions
apps/common/exception/custom_exception_handler.py
Other components
- HTTP client
- Django runtime
Connections 10
- HTTP client → Root routes: sends request
config/urls.py - Root routes → Content routes: routes prefix
config/urls.py - Content routes → Content view: dispatches to
apps/content/urls.py - Content view → JSON response: returns JSON
apps/content/views.py - WSGI entry → Django runtime: creates app
config/wsgi.py - ASGI entry → Django runtime: creates app
config/asgi.py - Django settings → Root routes: sets routing
config/settings.py - Django settings → SQLite database: configures database
config/settings.py - Django settings → Custom exceptions: configures handler
config/settings.py - Root routes → Custom exceptions: sets 404 handler
config/urls.py