Overview
frontend/.env.example documents several overlapping backend URLs with inconsistent defaults:
NEXT_PUBLIC_BACKEND_URL defaults to http://localhost:5000
NEXT_PUBLIC_API_URL defaults to http://localhost:3001
NEXT_PUBLIC_WS_URL defaults to ws://localhost:3001
Meanwhile backend/src/index.ts defaults to PORT = process.env.PORT || 3001. Features that read NEXT_PUBLIC_BACKEND_URL will point at a dead port in a default local setup, and it is unclear which var each feature should read.
Evidence
frontend/.env.example — the three URL vars and defaults
backend/src/index.ts — const PORT = process.env.PORT || 3001;
Acceptance Criteria
Files to Modify
frontend/.env.example
frontend/src/lib/ (API client config)
backend/src/index.ts (if port default changes)
Priority: Low
Overview
frontend/.env.exampledocuments several overlapping backend URLs with inconsistent defaults:NEXT_PUBLIC_BACKEND_URLdefaults tohttp://localhost:5000NEXT_PUBLIC_API_URLdefaults tohttp://localhost:3001NEXT_PUBLIC_WS_URLdefaults tows://localhost:3001Meanwhile
backend/src/index.tsdefaults toPORT = process.env.PORT || 3001. Features that readNEXT_PUBLIC_BACKEND_URLwill point at a dead port in a default local setup, and it is unclear which var each feature should read.Evidence
frontend/.env.example— the three URL vars and defaultsbackend/src/index.ts—const PORT = process.env.PORT || 3001;Acceptance Criteria
Files to Modify
frontend/.env.examplefrontend/src/lib/(API client config)backend/src/index.ts(if port default changes)Priority: Low