From a1bb5a58ff76f8226fd13a7001606ced542ab7d0 Mon Sep 17 00:00:00 2001 From: Saadi Myftija Date: Tue, 1 Sep 2026 10:09:03 +0200 Subject: [PATCH 1/2] docs: deploy build path flags, config file auto-detection Documents --native-build, --depot-build, --local-bundle, --detach and --build-logs in the deploy command reference, updates the GitHub integration's config file setting to describe auto-detection, and points the resource_exhausted troubleshooting entry at the --native-build flag. --- docs/github-integration.mdx | 2 +- docs/snippets/cli-commands-deploy.mdx | 24 ++++++++++++++++++++++++ docs/troubleshooting.mdx | 2 +- 3 files changed, 26 insertions(+), 2 deletions(-) diff --git a/docs/github-integration.mdx b/docs/github-integration.mdx index ffbc91f4321..8b23c8f75a6 100644 --- a/docs/github-integration.mdx +++ b/docs/github-integration.mdx @@ -34,7 +34,7 @@ This eliminates the need to manually run the `trigger.dev deploy` command or set Configure how your project is built: - - **Trigger config file**: Path to your `trigger.config.ts` file. By default, we look for it in the root of your repository. The path should be relative to the root of your repository and contain the config file name, e.g., `apps/tasks/trigger.config.ts`. + - **Trigger config file**: Auto-detected by default — we find your `trigger.config.ts` anywhere in your repository. Set a path relative to the root of your repository to override it, e.g., `apps/tasks/trigger.config.ts`. If your repository contains more than one config file, set the path of the one to use. - **Install command**: Auto-detected by default, but you can override it if necessary. The command will be run from the root of your repository. - **Pre-build command**: Run any commands before building and deploying your project, e.g., `pnpm run prisma:generate`. The command will be run from the root of your repository. diff --git a/docs/snippets/cli-commands-deploy.mdx b/docs/snippets/cli-commands-deploy.mdx index ce8125836aa..577d7a0f6b1 100644 --- a/docs/snippets/cli-commands-deploy.mdx +++ b/docs/snippets/cli-commands-deploy.mdx @@ -98,6 +98,30 @@ npx trigger.dev@latest deploy [path] briefly before it notices. Requires `--external-id`. + + Build the image on the Trigger.dev build server. Without a build flag, the server picks the build + path for your project. + + + + Build the image with Depot, ignoring any build path configured on the server. + + + + Install and bundle on your machine, then build the image on the build server from the uploaded + bundle. Requires `--native-build`. + + + + Exit once the build is queued instead of streaming the build logs. The deployment continues on + the build server. Requires `--native-build`. + + + + How build logs are shown: `compact` (default, a single updating line) or `full` (every log line). + CI and piped output always use `full`. + + Force building the deployment image locally using your local Docker. This is automatic when self-hosting. diff --git a/docs/troubleshooting.mdx b/docs/troubleshooting.mdx index 76fa76b0bee..04ef4275e45 100644 --- a/docs/troubleshooting.mdx +++ b/docs/troubleshooting.mdx @@ -87,7 +87,7 @@ Usually there will be some useful guidance below this message. If you can't figu ### `resource_exhausted` -If you see a `resource_exhausted` error during deploy, the build may have hit resource limits on our build infrastructure. Try our [native builder](https://trigger.dev/changelog/deployments-with-native-builds). +If you see a `resource_exhausted` error during deploy, the build may have hit resource limits on our build infrastructure. Try our [native builder](https://trigger.dev/changelog/deployments-with-native-builds) by deploying with the `--native-build` flag. ### `No loader is configured for ".node" files` From 7d1a662ddcb7fdfb5eed7aa79c9e4fe2d43afd63 Mon Sep 17 00:00:00 2001 From: Saadi Myftija Date: Tue, 1 Sep 2026 12:19:26 +0200 Subject: [PATCH 2/2] docs: tighten the deploy build flag descriptions --- docs/snippets/cli-commands-deploy.mdx | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/snippets/cli-commands-deploy.mdx b/docs/snippets/cli-commands-deploy.mdx index 577d7a0f6b1..1e808e35127 100644 --- a/docs/snippets/cli-commands-deploy.mdx +++ b/docs/snippets/cli-commands-deploy.mdx @@ -99,17 +99,13 @@ npx trigger.dev@latest deploy [path] - Build the image on the Trigger.dev build server. Without a build flag, the server picks the build - path for your project. - - - - Build the image with Depot, ignoring any build path configured on the server. + Use the native build server to install, bundle and build your project. Install and bundle on your machine, then build the image on the build server from the uploaded - bundle. Requires `--native-build`. + bundle. Requires `--native-build`. Use it if you prefer dependencies to be installed on your + machine rather than on the build server. @@ -117,15 +113,19 @@ npx trigger.dev@latest deploy [path] the build server. Requires `--native-build`. - - How build logs are shown: `compact` (default, a single updating line) or `full` (every log line). - CI and piped output always use `full`. + + Build the image with Depot, the default build provider. Force building the deployment image locally using your local Docker. This is automatic when self-hosting. + + How build logs are shown: `compact` (default, a single updating line) or `full` (every log line). + CI and piped output always use `full`. + + ### Common options These options are available on most commands.