cc @Kosai106 👋

the build suddenly fails
To be fair, the build never worked lol

;-;

Happy to provide any information needed to help debug this 😬 Would love to try out your service to get this project deployed

Anyway flagged to the team, I do have to dip for a call but we are looking into it.

(Unless you have time in an hour when I can go deep into this.)

I'll be around, thanks for the help so far!

Hey there @Kosai106 - so good-ish news, it's not a total platform issue, the bad news is that it may still be our fault here since we aren't properly detecting Turbo repo.

Oh! That's good-ish news

The errors that I am seeing now are much more dephicerable, its says:

WARN config production Use `--omit=dev` instead.

#13 0.566

#13 0.566 > build

#13 0.566 > turbo run build

#13 0.566

#13 0.570 sh: 1: turbo: not found

Ah, ,we're back to that error again. That's nice haha

I switched your workloads back over to the legacy system just so we can grok whats going on, I do suspect that you were running into platform related messes by way of what our build engineer was mentioning to us- however, Turbo availability is a tale as the end of time.

Okay, do what you must <:salute:1137099685417451530>

I just noticed that the build is installing dependencies with yarn install --frozen-lockfile but I'm running the scripts with npm run xxx which could explain why the error I'm now getting the error turbo: not found

But I'm not sure where the yarn command is defined 🤔 Only instances I'm seeing in the code is my GitHub actions but I'm not sure those are being used here

nixpacks will use yarn if it fines a yarn lock file, this would take priority over a package lock file

Ahhh, okay that's why. I use yarn myself. Good to know!

but as for turbo not being found, is it in your deps / dev deps? maybe you have it only installed locally globally

🤦‍♂️ I do have it installed, but it's as a dev dependency… That would explain it

afaik dev deps should be installed

but swap it over just to be sure

Yeah trying that now

Yeah that worked lol, I mean the build is still failing but it did find turbo now

progress!

whats the new error?

It's failing to build one of the websites and not the one I'm specifing the build for using --filter='@nextbanana/web' it's trying to also build @nextbanana/landing for some reason

how are you telling railway what build command to run?

by default nixpacks is going to run the build script

maybe also try specifying NIXPACKS_TURBO_APP_NAME

I specified the command in my railway.json

{
  "$schema": "https://railway.app/railway.schema.json",
  "build": {
    "builder": "NIXPACKS",
    "buildCommand": "npm run build --filter='@nextbanana/web'"
  },
  "deploy": {
    "numReplicas": 1,
    "startCommand": "npm run start --filter='@nextbanana/web'",
    "sleepApplication": false,
    "restartPolicyType": "ON_FAILURE",
    "restartPolicyMaxRetries": 10
  }
}

does the nixpacks build table state that it will be running those commands?

are you using node 18 to run this app locally?

Yes, I'm using Node 18.18.2 as specified in my .nvmrc

Okay, instead of specifying the filter in the railway.json, I added separate npm scripts in my root package.json and used those commands instead. This seems to work, though I'm not sure why there would be a difference.

that is very odd indeed, im not sure why either

Geez, the built image is 4.25GB

nixpacks is not known for small images

Haha good to know. Honestly I'm just happy to see this step at last

<:lfg:786867302888505364>

but does it work

Yes and no. The app launches, though it isn't picking up one of the environment variables so I get an error immediately lol

you have it set as a service variable?

Yes

It's complaining about the SESSION_SECRET_KEY var

@nextbanana/web:start: Error: You must provide the SESSION_SECRET_KEY environment variable in production.

is this a next app?

It's a Blitz.js app (Blitz is a layer on top of Next) https://blitzjs.com/

The build logs don't indicate an issue

its 32 characters right?

Yes, I just double checked

Anyway, it's 2am here now, we already got over the main issue which is great! I'll figure out the rest sometime tomorrow after work.

Thank you so much for your time @Brody as well as you @angelo ! Appreciate all the effort 🙏

happy to help!

We need a way to surface these common issues better- anyway, appreciate you bearing with us

@Brody I had to add the SESSION_SECRET_KEY as an env string in my turbo config. App is deployed and working now

And now I'll finally be able to sleep

ah I knew it was something like that, seen another user have to do something similar, but wasn't confident enough with the reason so I didn't say anything

but glad you got it working, when you have some down time to test stuff you can drop nixpacks and write a Dockerfile so you aren't ending up having to wait for a 2.25GB image to get pushed and pulled on every deployment