RAILWAY_PROJECT_NAME=>widdyup-backend-from-github

RAILWAY_SERVICE_NAME=>widdyup

RAILWAY_PROJECT_ID=>d6bfbe54-adbe-4e16-b4ff-badd7d915828

My Node.js monorepo, built with TypeScript, is configured for deployment via a validated Dockerfile located in the repository's root. Although Railway is integrated with my GitHub repository and automatically triggers deployments upon main branch changes, I've observed inconsistent behavior.

Specifically, Railway's project detection is not reliable: it occasionally recognizes the project as a Dockerfile deployment (the desired state), but at other times, it misidentifies it as a standard Node.js project, resulting in failed deployments.

I need guidance on how to configure Railway to consistently enforce Dockerfile-based deployments for this monorepo