How nithish07-cmd/devops-task-manager works
This is a small Flask task manager. Browser users manage tasks through rendered pages, while API clients can create, read, update, and delete tasks through REST endpoints. Both interfaces use JSON-file persistence; a separate health route supports uptime checks. Route and storage behavior is evidenced in app.py; the README documents the API and health capabilities.
Main entry points: app.py UI routes · index.html Task page · data.json Task records
Components 9
REST API
- API routes
app.py - Health route
app.py
Task storage
- Task file helpers
app.py - Task records
data.json
Other components
- Browser user
- API client
- Health monitor
Connections 10
- Browser user → UI routes: submits actions
- UI routes → Task file helpers: loads and saves
- UI routes → Task page: renders page
- Task page → Browser user: displays tasks
- API client → API routes: sends requests
- API routes → Task file helpers: loads and saves
- API routes → API client: returns JSON
- Task file helpers → Task records: reads and writes
- Health monitor → Health route: checks status
- Health route → Health monitor: returns OK