Custom Runtime Configuration

QuickDeploy uses Nixpacks to detect how to build and start a source project. Use nixpacks.toml when the detected commands do not match the application's production workflow.

Before changing the runtime configuration, confirm that the application:

• Has a production build and start command.
• Listens on 0.0.0.0, not only 127.0.0.1.
• Listens on the internal port passed through quickdeploy push --port. The default is 8080.

nixpacks.toml

Create this file in the source project root when the application needs explicit build or start commands:

[phases.build]
cmds = ["npm run build"]

[start]
cmd = "npm run start"

A whole reference of the configuration file can be found here.

If QuickDeploy reports Health check failed, inspect the container logs using the first-push troubleshooting steps. The check confirms that the process remains running; it does not request the public URL.