From d4473a9939bc2156c97bb2ab7522df4d66fc6f23 Mon Sep 17 00:00:00 2001 From: M Bernt Date: Fri, 1 Jul 2022 11:38:00 +0200 Subject: [PATCH] Update doc/source/admin/production.md Co-authored-by: Marius van den Beek --- doc/source/admin/production.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/source/admin/production.md b/doc/source/admin/production.md index 176c8e9d93d..a1eb91edf7e 100644 --- a/doc/source/admin/production.md +++ b/doc/source/admin/production.md @@ -164,10 +164,11 @@ as for running Galaxy. Thus its possible that tools modify data in Galaxy's Note that the tool only knows the paths to inputs and outputs, but if using the default configuration for other paths (e.g. configuration directory) also these paths are easily accessible. -There are two approaches to protect Galaxy against this: +There are three approaches to protect Galaxy against this: - Use different credentials for running tools. This can be configured using the ``real_system_username`` config variable. - Configure Galaxy to run jobs in a container and enable ``outputs_to_working_directory``. Then the tool will in an environment that allows write access only for the job working dir. All other paths will be accessible read only. +- Use pulsar to stage inputs and outputs For both more information can be found in the [job configuration](jobs.md) documentatiion and see also [using a compute cluster](cluster.md).