Railway Deployment #7787b4 fix: add backend package.json

[railway-app]

Problem

Railpack build failed with "No start command detected" because the service root directory backend/ had no package.json, so Railpack's Node provider couldn't be triggered, dependencies (express, cors, pg, dotenv, socket.io) couldn't be installed, and no start command could be resolved. Additionally, src/server.js hardcoded PORT=3000 and never read process.env.PORT, and listen() didn't bind to 0.0.0.0, which would prevent Railway from routing traffic even after a successful build.

Solution

Added backend/package.json declaring the runtime dependencies and a start script (node src/server.js) so Railpack detects the Node app, installs packages, and resolves a start command. Updated src/server.js to use process.env.PORT (falling back to 3000) and to bind server.listen to host 0.0.0.0, matching how Railway assigns and routes the port.

Changes

• Modified backend/src/server.js
• Created backend/package.json

Context

• Deployment: #7787b4
• Failed commit: 2c675c7

---

Generated by Railway