Skip to content

build: nixpacks.toml with the web app's install, build and start commands #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ralyodio merged 1 commit into from
Sep 25, 2026
Merged

build: nixpacks.toml with the web app's install, build and start commands #47

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions nixpacks.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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"
Loading