From ecf21aa071e92a41cd50908552ebb98a36c96eba Mon Sep 17 00:00:00 2001 From: Will Russell Date: Tue, 5 Nov 2024 14:18:42 +0000 Subject: [PATCH] fix: clarify task runner for cache example --- content/docs/14.best-practices/managing-pip-dependencies.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/14.best-practices/managing-pip-dependencies.md b/content/docs/14.best-practices/managing-pip-dependencies.md index 012fd9ad38..700495c89e 100644 --- a/content/docs/14.best-practices/managing-pip-dependencies.md +++ b/content/docs/14.best-practices/managing-pip-dependencies.md @@ -49,7 +49,7 @@ In either of these Kestra server installations, you will need to run the Python ## Using cache files -In a WorkingDirectory task, you can have the virtual environment setup, install all the pip package dependencies, and cache the `venv` folder. The pip package dependencies will then be cached as part of the virtual environment folder, and you need not install it on every execution of the flow. This is explained in detail in the [caching](../05.concepts/12.caching.md) page. +In a `WorkingDirectory` task, you can have the virtual environment setup with the [Process Task Runner](../task-runners/04.types/01.process-task-runner.md), install all the pip package dependencies, and cache the `venv` folder. The pip package dependencies will then be cached as part of the virtual environment folder, and you need not install it on every execution of the flow. This is explained in detail in the [caching](../05.concepts/12.caching.md) page. Here is a sample flow demonstrating how the `venv` folder can be cached: