How mwahidcodes/taskpipeline works
TaskPipeline is a task-tracking web app: users register or log in, then create, view, advance, and delete their own tasks on a status-column dashboard. The backend authenticates task requests and persists account and task data in PostgreSQL; it also exposes Prometheus metrics. The README provides only the product name, so capabilities and connections here rely on the sampled source and file tree. Registration UI exists in the tree, but its implementation was not sampled.
Main entry points: server.js HTTP server · App.jsx Page selection · Login.jsx Login form · Dashboard.jsx Task board
Components 15
Web application
- Page selection
frontend/src/App.jsx - Login form
frontend/src/pages/Login.jsx - Registration form
frontend/src/pages/Register.jsx - Task board
frontend/src/pages/Dashboard.jsx - Backend URL
frontend/src/config.js
Backend API
- HTTP server
backend/server.js - Auth routes
backend/routes/authRoutes.js - Task routes
backend/routes/taskRoutes.js - JWT authorization
backend/middleware/authMiddleware.js - Account operations
backend/controllers/authController.js - Task operations
backend/controllers/taskController.js
Persistence
- Database pool
backend/config/db.js - PostgreSQL
database/schema.sql
Other components
- User
- Prometheus scraper
Connections 17
- User → Page selection: uses
- Page selection → Login form: selects
- Page selection → Registration form: selects
- Page selection → Task board: opens
- Login form → Backend URL: gets URL
- Task board → Backend URL: gets URL
- Login form → HTTP server: submits login
- Task board → HTTP server: requests tasks
- HTTP server → Auth routes: dispatches
- HTTP server → Task routes: dispatches
- Auth routes → Account operations: dispatches
- Task routes → JWT authorization: checks token
- JWT authorization → Task operations: continues
- Account operations → Database pool: queries
- Task operations → Database pool: queries
- Database pool → PostgreSQL: reads/writes
- Prometheus scraper → HTTP server: scrapes metrics