Skip to content
Browse docs · Build behavior

Documentation

Build behavior

Build decisions follow your repository and project configuration.

Root and build strategy

The root directory is repository-relative. Use / for the repository root or a relative directory such as apps/web. Build detection inspects that root. A Dockerfile takes priority; otherwise a supported automatic adapter must match the project.

Framework selection alone does not make an unsupported repository buildable. Ambiguous or incomplete configurations fail with a deployment error rather than guessing an entrypoint.

Commands and health checks

Build and start command support depends on the selected adapter. Review Supported stacks before overriding commands. Your listening port is required and must match the application's actual port.

Set a health-check path such as /. A successful build still needs a runnable application and a passing HTTP health check. Check deployment events to distinguish build failure from startup or health-check failure.