From fe10f76aba446a12ac237d671a39ee260a581bc7 Mon Sep 17 00:00:00 2001 From: M Bernt Date: Fri, 1 Jul 2022 14:07:36 +0200 Subject: [PATCH] Update doc/source/admin/production.md Co-authored-by: Martin Cech --- doc/source/admin/production.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/source/admin/production.md b/doc/source/admin/production.md index cdd1a80ee66..f40eee952b7 100644 --- a/doc/source/admin/production.md +++ b/doc/source/admin/production.md @@ -167,7 +167,7 @@ Note that the tool only knows the paths to inputs and outputs, but if using the 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. +- Configure Galaxy to run jobs in a container and enable ``outputs_to_working_directory``. Then the tool will execute 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 More information on pulsar configuration can be found in the [job configuration](jobs.md) documentation, and the other two are explained in [using a compute cluster](cluster.md).