Browse Source

fix: restore railway and nixpacks

config to last known good state — revert bad
Node.js config that broke Python Railway deploy

Made-with: Cursor
pull/6453/head
Priyanka Punukollu 1 month ago
parent
commit
18d9f7c57c
  1. 1
      .node-version
  2. 2
      .npmrc
  3. 5
      nixpacks.toml
  4. 7
      railway.toml

1
.node-version

@ -1 +0,0 @@
20

2
.npmrc

@ -1,2 +0,0 @@
engine-strict=false
legacy-peer-deps=true

5
nixpacks.toml

@ -1,4 +1 @@
providers = ["node"] providers = ["python"]
[variables]
NIXPACKS_NODE_VERSION = "20"

7
railway.toml

@ -1,10 +1,9 @@
[build] [build]
builder = "nixpacks" builder = "nixpacks"
buildCommand = "npm ci --legacy-peer-deps && npx prisma generate && npm run build:production"
[deploy] [deploy]
startCommand = "npx prisma migrate deploy && npm run start" startCommand = "uvicorn main:app --host 0.0.0.0 --port $PORT"
healthcheckPath = "/api/v1/info" healthcheckPath = "/health"
healthcheckTimeout = 120 healthcheckTimeout = 60
restartPolicyType = "ON_FAILURE" restartPolicyType = "ON_FAILURE"
restartPolicyMaxRetries = 3 restartPolicyMaxRetries = 3

Loading…
Cancel
Save