5bce27d5-0216-4700-b2fc-f3a7f9644cba

It's in a constant loop just restarting, I think?

v2 builder?

No

[phases.build]
cmds = ["pnpm install"]  # we don't build anything, just install dependencies

[start]
cmd = 'pnpm run build && pnpm run start'

nixpacks.toml

been doing this for like 15 minutes

you're ending up installing packages twice, just use true as the build command

sure but i doubt thats the problem

show me the build plan after you've made the change

your screenshot, is that deploy or build logs?

Deploy

do you have resource limits set?

Yeah they're pretty low, 1Gb/1 VCPU

remove them please

kk

i.e. set to 8/8

done

let me know how that goes

honestly 50/50 chance i'll take off to Vercel at this point. I can't find any options for disabling SSG while maintaining runtime ISR

i wanted private networking to keep latency to my CMS low

that would be within your code

i mean yeah. i'm scouring docs rn but the closest thing I have found is obscure asf

someone else has to have done SSG on Railway without doing some insane setup

i would be surprised if one of the leading features of NextJS is unsupported on Railway

I've done SSG during build and SSR during runtime with Next, granted I didn't connect to a database, but it's possible

i mean i was doing that; i just added a network request to my CMS and now im fucked

aight now it's working

make sure you are using a health check, otherwise we would route traffic to your app while it's still building during runtime

yup that was screwing me immediately

I mean, use a heathcheck even if you weren't doing a build during runtime, it's just good practice 🙂

yea this project and most of mine tend to be hobbyist stuff

this one will eventually be an earner if i do it right

sweet!

part of why i kinda don't want to fool around with Railway right now. idk. i can switch if it's a goner, long build times and no caching is an L, but i can deal. maybe V2 builder will come along in the next few months

the fact that none of this stuff can be solved within NextJS makes me think it's intentional on their part

i wouldn't be considering switching to an edge platform if the build process was more configurable

we will be revisiting build v2 once we are fully on metal

i await

solved methinks

awesome

ur not gonna believe this the healthcheck refuses to work

`Attempt #8 failed with status 404:

your app returned a 404

it needs to return 200

wait i think i'm stupid

it's just a path not a host/port+path combo

correct, it's a healthcheck path

<:lfg:786867302888505364> this is a signal that i need to wind down for the night. brain is off

grab some carrots and ranch and have a chill night

!s