How gurungsh/dev-pulse-api works
dev-pulse-api is a small Express API for tracking service names and statuses. Clients list services with optional ID or case-insensitive name filters, or create and update records through the same endpoint; handlers use Prisma to access PostgreSQL. The source excerpt shows route registration and Prisma calls, while the README documents the API and database relationship. The schema and deployment templates are present in the tree but were not sampled, so their internal wiring is not expanded here.
Main entry points: index.ts Express server · schema.prisma Service data model
Components 7
API runtime
- Express server
src/index.ts - List services
src/index.ts - Create or update
src/index.ts
Service data
- Prisma access
src/index.ts - Service data model
prisma/schema.prisma - PostgreSQL
Other components
- API client
Connections 7
- API client → Express server: sends requests
README.md - Express server → List services: routes GET
src/index.ts - Express server → Create or update: routes POST
src/index.ts - List services → Prisma access: queries via
src/index.ts - Create or update → Prisma access: creates or updates
src/index.ts - Prisma access → PostgreSQL: reads and writes
README.md - Service data model → PostgreSQL: defines service table