You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/lifecycle.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,9 @@
2
2
3
3
## Summary
4
4
5
-
The purpose of the launcher is to minimize resource use by launching a runner on demand. To do so, the launcher impersonates a task runner until a task is ready for pickup, and then it launches a runner to run the task, and after the runner has automatically shut down, the launcher will re-launch a runner to pick up the next task.
5
+
The purpose of the launcher is to minimize resource use by launching a runner on demand.
6
+
7
+
To do so, the launcher impersonates a task runner until a task is ready for pickup, then it launches a runner to run the task, and after the runner has automatically shut down, the launcher will re-launch a runner once the next task is ready for pickup. The launcher follows this cycle independently for every runner type (i.e., language) configured to run.
@@ -90,6 +94,7 @@ Example config file at `/etc/n8n-task-runners.json`:
90
94
|`workdir`| Path where the task runner's `command` will run. |
91
95
|`command`| Command to start the task runner. |
92
96
|`args`| Args and flags to use with `command`. |
97
+
| `health-check-server-port` | Port for the runner's health check server. When a single runner is configured, this is optional and defaults to `5681`. When multiple runners are configured, this is required and must be unique per runner.
93
98
|`allowed-env`| Env vars that the launcher will pass through from its own environment to the runner. See [environment](environment.md). |
94
99
|`env-overrides`| Env vars that the launcher will set directly on the runner. See [environment](environment.md). |
95
100
@@ -104,8 +109,9 @@ The launcher can pass env vars to task runners in two ways, as specified in the
104
109
|`allowed-env`| Env vars filtered from the launcher's own environment | Passing env vars common to all runner types |
105
110
|`env-overrides`| Env vars set by the launcher directly on the runner, with precedence over `allowed-env`| Passing env vars specific to a single runner type |
106
111
107
-
Exceptionally, these three env vars cannot be disallowed or overridden:
112
+
Exceptionally, these four env vars cannot be disallowed or overridden:
0 commit comments