Skip to content

fix: use --env instead of --env-file in nixpacks build strat #44

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
Alimedhat000 merged 1 commit into from
May 29, 2026
Merged

fix: use --env instead of --env-file in nixpacks build strat #44

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
12 changes: 5 additions & 7 deletions packages/worker/src/deployments/strategies/nixpacks.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,13 +60,11 @@ function runNixpacksBuild(
args.push("--start-cmd", app.runCommand);
}

// Write env vars to a temporary file so secrets never appear on the command line.
const envFilePath = path.join(workspacePath, ".env");
const envFileContent = Object.entries(envMap)
.map(([k, v]) => `${k}="${v.replace(/"/g, '\\"')}"`)
.join("\n");
fs.writeFileSync(envFilePath, envFileContent, { mode: 0o600 });
args.push("--env-file", envFilePath);
// Pass env vars individually. In a container env, command-line
// args are not visible to other processes.
for (const [k, v] of Object.entries(envMap)) {
args.push("--env", `${k}=${v}`);
}

const proc = spawn("nixpacks", args, {
cwd: repoDir,
Expand Down
Loading