From 957f6dcda2212941a241a182b1cc71b527ba21f8 Mon Sep 17 00:00:00 2001 From: Anthony Ettinger Date: Fri, 25 Sep 2026 10:26:48 +0000 Subject: [PATCH] build: nixpacks.toml with the web app's install, build and start commands Railway built diskpush.com with RAILPACK_INSTALL_CMD, RAILPACK_BUILD_CMD and RAILPACK_START_CMD set on the service, so the build definition lived only in the dashboard. Any nixpacks builder (dev2) failed with "No start command could be found" because the root package.json has none. Same three commands, in the repo. Co-Authored-By: Claude Fable 5.1 --- nixpacks.toml | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 nixpacks.toml diff --git a/nixpacks.toml b/nixpacks.toml new file mode 100644 index 0000000..97f90ca --- /dev/null +++ b/nixpacks.toml @@ -0,0 +1,16 @@ +# How the diskpush.com web app is built and started when the builder is nixpacks +# (dev2, and anywhere else that is not Railway). Railway held the same three +# commands in its RAILPACK_INSTALL_CMD / RAILPACK_BUILD_CMD / RAILPACK_START_CMD +# service variables, which no other builder can see. The root package.json has +# no start script on purpose: the web app is one workspace of several. +[phases.install] +cmds = [ + "npm install -g corepack@0.24.1 && corepack enable", + "pnpm install --frozen-lockfile --prod=false --filter @diskpush/web...", +] + +[phases.build] +cmds = ["pnpm --filter @diskpush/web build"] + +[start] +cmd = "pnpm --filter @diskpush/web start"