How better-tracker/tracker-mono works
Project Tracker is currently a workspace skeleton, not a functioning tracker: the web page only reports that it is running, the API returns 404s, and mobile and shared packages are empty boundaries. The principal available workflow is a user opening the web app; separately, the API starts and listens for requests. The README documents mobile and local PostgreSQL as development options, but the API does not connect to PostgreSQL. Project route, controller, and service files describe intended roles only; no active route wiring is shown.
Main entry points: server.ts API server · page.tsx Web home · mobile Mobile app · app.ts Fastify app
Components 12
Application shells
- Web home
apps/web/src/app/page.tsx - Mobile app
apps/mobile
API boundary
- API server
apps/api/src/server.ts - Fastify app
apps/api/src/app.ts - Project routes
apps/api/src/modules/projects/projects.routes.ts - Project controller
apps/api/src/modules/projects/projects.controller.ts - Project service
apps/api/src/modules/projects/projects.service.ts
Reserved packages
- API contracts
packages/contracts/src/index.ts - API client
packages/api-client/src/index.ts - Database boundary
packages/database/src/index.ts
Local database
- PostgreSQL
compose.yml
Other components
- User
Connections 4
- User → Web home: opens
README.md - User → Mobile app: runs
README.md - User → API server: requests
README.md - API server → Fastify app: builds
apps/api/src/server.ts