How negisushant/dpi-uptime works
Project type and purpose
• This is a Turborepo-managed monorepo that houses multiple TypeScript apps and shared packages.
• It implements a full-stack platform composed of:
• A Next.js-based frontend (“apps/frontend”)
• A Node-based API service (“apps/api”)
• Two background services or “workers” (“apps/hub” and “apps/validator”)
• Shared libraries: a UI component library, common utilities, a Prisma-based DB layer, plus linting/TS configs.
File structure
• Top-level “apps/” directory contains deployable units:
• frontend (Next.js UI)
• api (HTTP server + middleware + types)
• hub (background worker)
• validator (background worker)
• “packages/” directory contains internal libs:
• common – shared functions and types
• db – Prisma ORM, migrations, database client
• ui – React component library
• eslint-config, typescript-config – developer tooling
• Root includes turbo.json for task orchestration, pnpm or npm locks, and global configs.
README for additional insights
• Confirms Next.js apps and shared TS packages.
• Emphasizes Turborepo features: task running, caching, remote cache integration.
Main components & interactions
a. Components (runtime view)
• Frontend App (Next.js)
• API Service (Node/Express or Next API routes)
• Hub Worker (Node script)
• Validator Worker (Node script)
• Database (PostgreSQL or similar behind Prisma)
• Turborepo Orchestrator (build/dev tool, not in runtime)
b. Relationships
• Frontend ↔ API: HTTP/REST or fetch/JSON calls
• API → Database: Prisma client reads/writes
• Hub & Validator → API or Database: likely consume tasks via API endpoints or direct DB polling
c. Architectural patterns
• Monorepo with code sharing (packages/)
• Service separation: UI layer, API layer, background workers
• Shared-library pattern for UI components and utility code
• Prisma as Data-Access-Layer (DAL)
d. Key technologies
• Next.js, React, TypeScript (frontend)
• Node.js, Express or built-in Next API (backend)
• Prisma ORM + migrations (packages/db)
• PNPM/Turbo (monorepo orchestration)
• Shared UI via packages/ui
• Shared logic via packages/common