Reword sentence

Co-authored-by: Nicola Soranzo <nicola.soranzo@earlham.ac.uk>
This commit is contained in:
davelopez
2024-04-10 17:03:55 +02:00
co-authored by Nicola Soranzo
parent f3b968adf6
commit 4ec8cef337
3 changed files with 4 additions and 4 deletions
+2 -2
View File
@@ -5156,8 +5156,8 @@
to set the `result_backend` option in the `celery_conf` option to
a valid Celery result backend URL. By default, Galaxy uses an
SQLite database at '<data_dir>/results.sqlite' for storing task
results. Please use a more robust backend for production setups
like Redis. For details, see
results. Please use a more robust backend (e.g. Redis) for
production setups. For details, see
https://docs.galaxyproject.org/en/master/admin/production.html#use-celery-for-asynchronous-tasks
:Default: ``false``
:Type: bool
+1 -1
View File
@@ -2763,7 +2763,7 @@ galaxy:
# set the `result_backend` option in the `celery_conf` option to a
# valid Celery result backend URL. By default, Galaxy uses an SQLite
# database at '<data_dir>/results.sqlite' for storing task results.
# Please use a more robust backend for production setups like Redis.
# Please use a more robust backend (e.g. Redis) for production setups.
# For details, see
# https://docs.galaxyproject.org/en/master/admin/production.html#use-celery-for-asynchronous-tasks
#enable_celery_tasks: false
+1 -1
View File
@@ -3765,7 +3765,7 @@ mapping:
configured the `celery_conf` option below. Specifically, you need to set the
`result_backend` option in the `celery_conf` option to a valid Celery result
backend URL. By default, Galaxy uses an SQLite database at '<data_dir>/results.sqlite' for storing task results.
Please use a more robust backend for production setups (e.g. Redis).
Please use a more robust backend (e.g. Redis) for production setups.
For details, see https://docs.galaxyproject.org/en/master/admin/production.html#use-celery-for-asynchronous-tasks
celery_conf: