Matching Service: - Fetch manual matches at start of runMatching() (suggestionId: null) - Build manualBlockedPairs set with both directions (A:B and B:A) - Skip recorder candidates if manual match exists between dancer and recorder - Ensures no duplicate matches on /matches page - Manual match = user-controlled, algorithm respects user decisions Documentation (docs/TODO.md): - Add comprehensive matching system test scenarios (S1-S16) - Document 4 critical gaps (P0): ratings/stats, admin middleware, participant validation - Document 3 high priority items (P1): cleanup conflicts, rate limiting, notifications - Document 6 medium priority items (P2): audit endpoints, zombie cleanup, reminders - List 11 edge cases for team discussion (E1-E11) - Clear priority ranking and questions for team Critical Findings: - recordingsDone/recordingsReceived fields exist but NEVER updated (fairness broken!) - Admin endpoints lack security middleware - Inconsistent event participant validation across endpoints Test Coverage: - S1-S7: Implemented (basic flow, collisions, limits, manual vs auto) - S10: NOT IMPLEMENTED - ratings/stats system (CRITICAL!) - S11: Partially implemented - audit trail exists, API endpoints missing - S14: Partially implemented - recorder-only auth works, admin middleware missing - S15-S16: NOT IMPLEMENTED - security, notifications
spotlight.cam Backend
Node.js + Express backend for spotlight.cam - P2P video exchange app for dance events.
Features
- ✅ Express REST API
- ✅ CORS enabled
- ✅ Health check endpoint
- ✅ Error handling
- ✅ Unit tests (Jest + Supertest)
- ⏳ PostgreSQL integration (planned)
- ⏳ JWT authentication (planned)
- ⏳ Socket.IO for real-time chat (planned)
- ⏳ WebRTC signaling (planned)
API Endpoints
Health Check
GET /api/health- Backend health status
Future Endpoints
POST /api/auth/register- Register new userPOST /api/auth/login- Login userGET /api/users/me- Get current userGET /api/events- List eventsPOST /api/matches- Create matchPOST /api/ratings- Rate partner
Development
Install dependencies
npm install
Run in development mode
npm run dev
Run tests
npm test
Run tests in watch mode
npm run test:watch
Run in production mode
npm start
Environment Variables
Create a .env file (see .env.example):
NODE_ENV=development
PORT=3000
CORS_ORIGIN=http://localhost:8080
Project Structure
backend/
├── src/
│ ├── __tests__/ # Unit tests
│ │ └── app.test.js
│ ├── routes/ # API routes (future)
│ ├── controllers/ # Business logic (future)
│ ├── middleware/ # Custom middleware (future)
│ ├── utils/ # Helper functions (future)
│ ├── app.js # Express app setup
│ └── server.js # Server entry point
├── .env # Environment variables (gitignored)
├── .env.example # Environment variables template
├── package.json
└── Dockerfile
Testing
Tests are written using:
- Jest - Test framework
- Supertest - HTTP assertions
Run tests:
npm test
Current test coverage:
- Health check endpoint
- 404 error handling
- CORS configuration
- JSON body parsing
Docker
Build and run with Docker Compose (from project root):
docker compose up --build
Backend will be available at:
- Internal: http://backend:3000
- Through nginx: http://localhost:8080/api
Next Steps
- ✅ Basic Express setup
- ✅ Health check endpoint
- ✅ Unit tests
- ⏳ PostgreSQL connection
- ⏳ Database schema and migrations
- ⏳ Authentication (JWT + bcrypt)
- ⏳ Socket.IO for real-time chat
- ⏳ WebRTC signaling
License
TBD