fix: wrap Railway startCommand in sh -c so $PORT expands

[timothylee58]

Summary

Railway does not shell-interpolate env vars in startCommand — $PORT was passed literally to uvicorn, which rejected it as a non-integer.

Fix: wrap in sh -c '...' so the shell expands $PORT before uvicorn sees it.

startCommand = "sh -c 'uvicorn app.main:app --host 0.0.0.0 --port $PORT --workers 2'"

Also remove the custom start command from the Railway dashboard if one is set there — railway.toml takes precedence when deployed via Dockerfile builder.

https://claude.ai/code/session_017cLXjZu6kkjXRf2BemMPpp

---

Generated by Claude Code

---

Summary by cubic

Fix Railway deploys by wrapping the startCommand in sh -c so $PORT expands at runtime. Uvicorn now binds to the platform-assigned port instead of a hardcoded value.

• Migration
  • If a custom start command exists in the Railway dashboard, remove it. railway.toml is used for Dockerfile builds.

^{Written for commit 5f4bbe6. Summary will update on new commits. Review in cubic}

[netlify]

✅ Deploy Preview for bajet-buddy canceled.

Name	Link
🔨 Latest commit	5f4bbe6
🔍 Latest deploy log	https://app.netlify.com/projects/bajet-buddy/deploys/6a1404f4c78c360008d81a8c

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	bajet-buddy	5f4bbe6	May 25 2026, 08:15 AM

[gemini-code-assist]

Code Review

This pull request updates the railway.toml configuration to use the $PORT environment variable for the uvicorn server instead of a hardcoded value. The review feedback suggests using exec to ensure the application correctly receives termination signals and providing a default value for the port variable to improve reliability.

[gemini-code-assist]

To ensure that the application receives termination signals (like SIGTERM) correctly and to provide a fallback port if the $PORT environment variable is missing, consider using exec and a default value for the port. This also maintains consistency with the implementation in the Dockerfile.

Suggested change

	startCommand = "sh -c 'uvicorn app.main:app --host 0.0.0.0 --port $PORT --workers 2'"
	startCommand = "sh -c 'exec uvicorn app.main:app --host 0.0.0.0 --port ${PORT:-8080} --workers 2'"