9 months ago
Today I started using railway.toml config-as-a-file. When I deploy my project (nodejs 22, pnpm 9), it failed because Nixpacks was using pnpm-8 instead of pnpm-9. I compared the build logs to the one I've made yesterday and I noticed that today I used Nixpacks v1.24 and yesterday v1.29.
Don't know if you had to downgrade today by chance or if there is a bug with railway.toml
0 Replies
My railway.toml
"$schema" = "https://railway.com/railway.schema.json"
[build]
buildEnvironment = "V2"
builder = "NIXPACKS"
nixpacksConfigPath = "nixpacks.toml"
buildCommand = "pnpm build"
[deploy]
runtime = "V2"
preDeployCommand = "pnpm prisma migrate deploy"
startCommand = "pnpm start"
healthcheckPath = "/api/health"
healthcheckTimeout = 300
sleepApplication = false
[deploy.limitOverride.containers]
cpu = 1
memoryBytes = 1_000_000_000and nixpacks.toml
[variables]
TZ = 'America/Argentina/Buenos_Aires'9 months ago
quick question, where did [deploy.limitOverride.containers] come from? thats not valid syntax im dumb
9 months ago
are you sure you didnt fix your nixpacks version to v1.24.1?
you are also using unmaintained v2 builder, we can't recommend doing that right now
9 months ago
awsome
9 months ago
!s
Status changed to Solved brody • 9 months ago