Nixpacks Configuration File (nixpacks.toml)

Projects can override or extend the auto-detected build plan by committing a `nixpacks.toml` (or `nixpacks.json`) file at the root of the repository. The configuration file mirrors the build-plan structure with top-level `providers`, `buildImage`, `variables`, and `staticAssets`, a `[phases.]` table for each phase carrying `cmds`, `nixPkgs`, `nixLibs`, `aptPkgs`, `dependsOn`, `cacheDirectories`, `onlyIncludeFiles`, and `paths`, and a `[start]` table for `cmd`, `runImage`, and runtime-only file inclusion. The `"..."` token can be used inside array fields to extend rather than replace provider-supplied values.

Nixpacks Configuration File (nixpacks.toml) is one of 5 APIs that Nixpacks publishes on the APIs.io network.

Tagged areas include Configuration, TOML, Phases, and Customization. The published artifact set on APIs.io includes API documentation and an API reference.

API entry from apis.yml

apis.yml Raw ↑
aid: nixpacks:configuration-file
name: Nixpacks Configuration File (nixpacks.toml)
description: Projects can override or extend the auto-detected build plan by committing a `nixpacks.toml`
  (or `nixpacks.json`) file at the root of the repository. The configuration file mirrors the build-plan
  structure with top-level `providers`, `buildImage`, `variables`, and `staticAssets`, a `[phases.<name>]`
  table for each phase carrying `cmds`, `nixPkgs`, `nixLibs`, `aptPkgs`, `dependsOn`, `cacheDirectories`,
  `onlyIncludeFiles`, and `paths`, and a `[start]` table for `cmd`, `runImage`, and runtime-only file
  inclusion. The `"..."` token can be used inside array fields to extend rather than replace provider-supplied
  values.
humanURL: https://nixpacks.com/docs/configuration/file
tags:
- Configuration
- TOML
- Phases
- Customization
properties:
- type: Documentation
  url: https://nixpacks.com/docs/configuration/file
- type: Reference
  url: https://nixpacks.com/docs/configuration/environment