PulseBackEnd

A secure Node.js, Express, and Prisma API for the Pulse wellness tracker.

Features

• TypeScript development with ts-node
• JWT-based user authentication
• HTTPS server with bundled certificates
• CRUD check-in endpoints for moods, emotions, sleep, health items, hobbies, social activities, chores, productivity, and weather
• Analytics endpoints for mood trends, emotion clouds, sleep trends, productivity trends, and item frequency clouds
• PostgreSQL schema defined with Prisma
• Per-user data access enforced in code
• .env configuration for secrets and database connection

Setup

1. Install dependencies with npm install.
2. Create a .env file and define DATABASE_URL, JWT_SECRET, and PORT.
3. Push the schema to your database with npx prisma db push.
4. Start the development server with npm run dev. For production, run npm run build then npm start.

Database Schema

The full schema resides in prisma/schema.prisma. It creates tables for users, check-ins, and all related metadata enums.

API Endpoints

• POST /api/auth/register – Register a new user
• POST /api/auth/login – Login and receive a JWT
• GET /api/checkins – Retrieve check-ins for the authenticated user
• POST /api/checkins – Add a new check-in
• GET /api/analytics/mood-trend – Mood scores over time
• GET /api/analytics/emotion-cloud – Emotion frequency for a date range
• GET /api/analytics/sleep-trend – Sleep quality trend
• GET /api/analytics/productivity-trend – Productivity trend
• GET /api/analytics/health-cloud – Health item frequency
• GET /api/analytics/hobby-cloud – Hobby frequency
• GET /api/analytics/social-cloud – Social interaction frequency
• GET /api/analytics/chore-cloud – Chore frequency
• GET /api/analytics/weather-cloud – Weather condition frequency

Security

All endpoints except register and login require a valid JWT. The server isolates user data based on the token payload, and secrets remain in the server environment.