How part47/minimal-web-app works
This is a minimal Python HTTP application for showing which backend instance handled a request. The main workflow is an HTTP GET routed by the handler into an HTML, JSON, or health/readiness response; the informational endpoints include per-process identity and request statistics. The README also describes running identical instances behind a reverse proxy, but no proxy configuration or implementation is present in the repository.
Main entry points: app.py GET handler
Components 10
HTTP runtime
- HTTP server
app.py
Request handling
- GET handler
app.py - Request counter
app.py - Node information
app.py
Response output
- HTML page
app.py - JSON response
app.py - Health checks
app.py - HTTP response sender
app.py
Other components
- HTTP client
- Reverse proxy
Connections 14
- HTTP client → Reverse proxy: sends requests
README.md - Reverse proxy → HTTP server: balances requests
README.md - HTTP client → HTTP server: requests directly
README.md - HTTP server → GET handler: configures handler
app.py - GET handler → Request counter: increments counter
app.py - GET handler → Node information: builds details
app.py - GET handler → HTML page: formats page
app.py - GET handler → JSON response: encodes JSON
app.py - GET handler → Health checks: serves checks
app.py - GET handler → HTTP response sender: sends response
app.py - HTML page → HTTP response sender: provides body
app.py - JSON response → HTTP response sender: provides body
app.py - Health checks → HTTP response sender: provides body
app.py - HTTP response sender → HTTP client: returns response
app.py