Build Configuration
How Out Plane turns your repository into a running application.
When you deploy from Git, Out Plane builds your repository into a runnable image. You choose how with the build method. Prebuilt image apps skip this step entirely.
Build Methods
| Method | What it does |
|---|---|
| Dockerfile | Builds with your repository's Dockerfile. Full control over the image. |
| Buildpacks | Detects your language and builds the app for you, with no Dockerfile. |
Dockerfile Detection
When the build method is Dockerfile, Out Plane scans the selected branch and
root directory for a Dockerfile. If it finds one, the create screen
previews it and prefills the ports and environment variables it detects from the final
build stage. If none is found, you set ports and variables yourself.
Root Directory
If your app lives in a subdirectory of the repository (for example a monorepo), set the
root directory to that path. It is the build context, and the Dockerfile is looked
up relative to it. The default is the repository root, /.
Start Command
The start command runs as a direct exec, not through a shell. Leave it empty to use
the image default. For shell features such as &&, $VAR, or pipes, wrap it yourself:
sh -c "npm run migrate && npm start"Build Filters
For Git apps you can limit which changes trigger a build, with an allow list and an ignore list of glob patterns. Ignore rules win over allow rules, and a manual deploy ignores both.