From 420216b1fe586b7e8c6c7f637c5c65dd53d3537a Mon Sep 17 00:00:00 2001 From: letroglodyte Date: Thu, 29 Jan 2026 12:33:01 +0100 Subject: [PATCH] feat: modified server deployment configuration --- docs/server/configuration.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/server/configuration.md b/docs/server/configuration.md index ea5487c..fd3fde1 100644 --- a/docs/server/configuration.md +++ b/docs/server/configuration.md @@ -68,11 +68,13 @@ Each queue is defined by its name (key) and the following options: |--------|------|----------|-------------| | `git_url` | string | Yes | Git repository URL for task code | | `branch` | string | Yes | Git branch to clone | +| `code_path` | string | No | Path of the task code within the repository (e.g., `simple-task`) | | `startup_cmd` | string | Yes | Command to start the Python process | | `startup_timeout_secs` | int | Yes | Timeout for process startup | | `requirements_file` | string | No | Path to requirements.txt (default: `requirements.txt`) | | `vaults` | list | No | List of vault names to inject as environment variables | | `redis_storage` | bool | No | If `true`, task results are written to Redis. If `false`, results are not stored in Redis and must be managed by the task itself (e.g., via webhook). Default: `false` | +| `git_token` | string | No | Path to your github PAT's. Use the following format `vault://{VAULT-NAME}/{KEY}` (e.g., `vault://github_pats/SIMPLE_TASK`) | ## Sub-Queues