🏗️ Architecture: What are the critical issues blocking backend-vitto-api Rail...

Date: 2026-02-07
Time: 19:35:27 UTC
Session: editor2-98.3
Agent: backend
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

What are the critical issues blocking backend-vitto-api Railway deployment?

Task: Session 99: Vitto Railway production deployment audit

🎯 Decision Made

Chosen:

10 issues identified: 3 CRITICAL (main.ts missing Railway PORT detection, missing isRailway production guard, CORS missing production origins), 4 HIGH (no Railway project, no deploy branch, no deploy script, missing package.json commands), 3 MEDIUM/LOW (MongoDB URI for production, missing reference config, Dockerfile HEALTHCHECK default port)

Options Considered:

• No alternatives documented

💭 Reasoning

Audited backend-vitto-api against established Railway deployment patterns from backend-ai-api and backend-api. The most critical bug is main.ts reading VITTO_API_PORT instead of Railway's dynamic PORT — this will cause every deployment to fail because Railway assigns PORT (usually 8080) but the app binds to 3003. Also identified that no Railway project, deploy branch, or deploy script exists yet. Side finding: backend-api health endpoint at api.gograb.space returns 404.

📁 Files Involved

• apis/backend-vitto-api/src/main.ts
• deployment/Dockerfile.railway.backend-vitto
• apis/backend-vitto-api/railway.json
• .railway/projects.json
• package.json

🔗 Related

• Decision ID: dev_1770492927513_uejil7e
• Session: 98
• Workspace: editor2

Auto-generated by MCP Smart Consolidation