phlx
WWasp-lang
•Created by phlx on 11/1/2024 in #đŸ™‹questions
Timeout error when deploying railway up
@martinsos I tried deploying in fly as well. I don't have issues when deploying the frontend but the backend simply doesnt start. That's why I tried using railway but it has that issue of not supporting projects with more than 45 mb, I could use railway up but it would require a different configuration than what's described in the docs. I think the github action would work if the app deployment works right? Its more for continuous deployment, but in my case it doesn't deploy the first time correctly. I'll look into the learning materials, thanks!
8 replies
WWasp-lang
•Created by phlx on 11/1/2024 in #đŸ™‹questions
Machine doesn't start stays at waiting for machine to be reachable
@martinsos Yeah I also tried manual deployment and changing the first line in the generated Dockerfile in .wasp/build to ubuntu but I still had the same issue in deployment đŸ˜”
16 replies
WWasp-lang
•Created by phlx on 11/1/2024 in #đŸ™‹questions
Machine doesn't start stays at waiting for machine to be reachable
Tried everything but didn't work đŸ˜¦
16 replies
WWasp-lang
•Created by phlx on 11/1/2024 in #đŸ™‹questions
Machine doesn't start stays at waiting for machine to be reachable
@kapa.ai Database is looking good, no issues in the logs its running normally, I have the enviroment variables my app uses in flyctl secrets myserver. There isn't any errors in the logs of the server, it just stops after trying to start multiple times. The port its 3001 in fly.toml and also in the fly secrets. Tried wasp deploy fly deploy and still with the issue. I'll try removing one of the libraries that node-alpine doesn't support but this would make my app unusable even if it deploys correctly
16 replies