10 months ago
The following project deployment works only with builder "nixpacks". It does not work if I remove it.
Has anyone faced issue and can help me out what might be causing the issue.
16 Replies
10 months ago
buildCommand = "cd packages/convex-backend && npx convex deploy --cmd 'cd ../../ && pnpm build:starter-convex' --cmd-url-env-var-name NEXT_PUBLIC_CONVEX_URL"
i do have it --> pnpm build:starter-convex in the above and then
startCommand = "pnpm start:starter-convex"
samgordon
Hi, Please add `next build` to your build command.
10 months ago
buildCommand = "cd packages/convex-backend && npx convex deploy --cmd 'cd ../../ && pnpm build:starter-convex' --cmd-url-env-var-name NEXT_PUBLIC_CONVEX_URL"
i do have it --> pnpm build:starter-convex in the above and then
startCommand = "pnpm start:starter-convex"
varunteja007006
buildCommand = "cd packages/convex-backend && npx convex deploy --cmd 'cd ../../ && pnpm build:starter-convex' --cmd-url-env-var-name NEXT\_PUBLIC\_CONVEX\_URL" i do have it --> pnpm build:starter-convex in the above and then startCommand = "pnpm start:starter-convex"
10 months ago
What does build:starter-convex do?
samgordon
Hi, Please add `next build` to your build command.
10 months ago
I have 1 more doubt, Is it safe to upload logs? I can help upload the logs success one with nixpacks and another with RAILPACK which failed.
I hope it does not have any sensitive information. Could you please confirm.
samgordon
What does `build:starter-convex` do?
10 months ago
"build:starter-convex": "turbo build --filter=starter-convex",
Since its a turbo repo it will build the next app with shared packages as well.
10 months ago
Do you see just a build part of your script anywhere? It keeps chaining down to that command.
samgordon
Yes, it is safe to upload logs.
10 months ago
samgordon
Do you see just a `build` part of your script anywhere? It keeps chaining down to that command.
10 months ago
Its actually confusing because when I set builder = "nixpacks" in .toml it works but not when I set it to builder = "RAILPACK".
I will try to debug that build sequence via logs and if possible ssh
varunteja007006
Its actually confusing because when I set builder = "nixpacks" in .toml it works but not when I set it to builder = "RAILPACK". I will try to debug that build sequence via logs and if possible ssh
10 months ago
I would try to deploy it myself but Railway has horrible caching policies and I won't be able to deploy this repository for a while.
Can you try setting your start command to be sleep 999999, ssh into the container, and try to find where the .next directory or any build directory is located?
samgordon
I would try to deploy it myself but Railway has horrible caching policies and I won't be able to deploy this repository for a while. Can you try setting your start command to be `sleep 999999`, ssh into the container, and try to find where the .next directory or any build directory is located?
10 months ago
I was able to ssh into the successful part of deploy not the failed one. Is it possible to ssh into the failed container?
sleep 999999 --> in the .toml file?
10 months ago
https://gemini.google.com/share/fa8d739c601d
Made an analysis with AI.
samgordon
I would try to deploy it myself but Railway has horrible caching policies and I won't be able to deploy this repository for a while. Can you try setting your start command to be `sleep 999999`, ssh into the container, and try to find where the .next directory or any build directory is located?
10 months ago
Thanks that sleep command did help i dont see the .next folder when I ssh into the container. Its strange I am not sure if I have to update my deploy logic or something wrong with the way RAILPACK works. What do you suggest?
10 months ago
Had to update the script for it to work. Must be the way railpack reads the script i guess.
Thanks a lot Sam
Attachments
Status changed to Solved samgordon • 10 months ago