2 years ago
Response from ChatGPT -
It looks like your build process is taking too long and getting cut off because it's running a command (node server.js) that starts your server during the build. Normally, when you're preparing to deploy a website, the build command should be doing things like processing your code but not actually running the server. That should happen later, once the build is successful and the site is being served to visitors. To fix this, you'll want to adjust your npm run build command in your package.json file so it's set up just to prepare your site for launch, not to start the server. This way, it won't time out and should complete successfully. Check your documentation or logs if you need specific settings for this, and make sure the build and server start commands are kept separate.
ⓘ Deployment information is only viewable by Project members and Railway admins.
2 Replies
2 years ago
If your build script does, in fact, try to start your server, then ChatGPT is correct, and you should move your start command to a start script instead.
Status changed to Solved Railway • almost 2 years ago
2 years ago
It's up now! There were some inconsistencies with file paths too. It's all resolved now. Thank you!