Railway server deploy errors
I get this error after railway up while following the guide in OpenSaaS
3 Replies
Hi @Fizz. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the information provided in the knowledge sources, it appears that you're encountering an issue while deploying your Wasp application to Railway. The error suggests that the
wasp build command is not recognized in the Docker environment. Let me provide some guidance on how to address this:
1. First, it's important to note that the wasp build command should be run locally, not in the Docker container. According to the Wasp deployment documentation, you should run wasp build on your local machine before deploying.
2. The correct deployment process for Railway, as outlined in the Railway deployment guide, involves the following steps:
a. Run wasp build locally to generate the deployable code.
b. Navigate to the .wasp/build/ directory.
c. Link your app to the Railway project using railway link.
d. Set up the required environment variables in the Railway dashboard.
e. Deploy using railway up.
3. The Dockerfile generated by Wasp should not include the wasp build command. If you've customized the Dockerfile, you might need to update it. As mentioned in the migration guide, if you're using a custom Dockerfile, you should check the newly generated one in .wasp/out/Dockerfile and incorporate any necessary changes.
4. If you're following the OpenSaaS guide, make sure it's up-to-date with the latest Wasp deployment practices. The official Wasp documentation should be your primary reference for deployment steps.
To resolve this issue:
1. Run wasp build locally first.
2. Navigate to the .wasp/build/ directory.
3. Make sure your Dockerfile doesn't include the wasp build command.
4. Try deploying again with railway up.
If you continue to face issues, you might want to check if there are any specific Railway configuration files or settings that could be causing conflicts with the Wasp-generated setup.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Fizz, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?@miho or @Filip to double check whether what Kapa says makes sense 🙂
@Fizz could you share more of the errors message? Only error code 127 doesn't mean much 🙂