Move result_backend comment to celery_conf

Co-authored-by: Nicola Soranzo <[email protected]>

doc/source/admin/galaxy_options.rst

@@ -5156,8 +5156,7 @@
     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 (e.g. Redis) for
-    production setups. For details, see
+    results. For details, see
     https://docs.galaxyproject.org/en/master/admin/production.html#use-celery-for-asynchronous-tasks
 :Default: ``false``
 :Type: bool
@@ -5175,7 +5174,8 @@
     The `broker_url` option, if unset or null, defaults to the value
     of `amqp_internal_connection`. The `result_backend` option, if
     unset or null, defaults to an SQLite database at
-    '<data_dir>/results.sqlite' for storing task results.
+    '<data_dir>/results.sqlite' for storing task results. Please use a
+    more robust backend (e.g. Redis) for production setups.
     The galaxy.fetch_data task can be disabled by setting its route to
     "disabled": `galaxy.fetch_data: disabled`. (Other tasks cannot be
     disabled on a per-task basis at this time.)

lib/galaxy/config/sample/galaxy.yml.sample

@@ -2763,7 +2763,6 @@ 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 (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
@@ -2775,7 +2774,8 @@ galaxy:
   # The `broker_url` option, if unset or null, defaults to the value of
   # `amqp_internal_connection`. The `result_backend` option, if unset or
   # null, defaults to an SQLite database at '<data_dir>/results.sqlite'
-  # for storing task results.
+  # for storing task results. Please use a more robust backend (e.g.
+  # Redis) for production setups.
   # The galaxy.fetch_data task can be disabled by setting its route to
   # "disabled": `galaxy.fetch_data: disabled`. (Other tasks cannot be
   # disabled on a per-task basis at this time.)

lib/galaxy/config/schemas/config_schema.yml

@@ -3765,7 +3765,6 @@ 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 (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:
@@ -3785,7 +3784,7 @@ mapping:
 
           The `broker_url` option, if unset or null, defaults to the value of `amqp_internal_connection`.
           The `result_backend` option, if unset or null, defaults to an SQLite database at '<data_dir>/results.sqlite'
-          for storing task results.
+          for storing task results. Please use a more robust backend (e.g. Redis) for production setups.
 
           The galaxy.fetch_data task can be disabled by setting its route to "disabled": `galaxy.fetch_data: disabled`.
           (Other tasks cannot be disabled on a per-task basis at this time.)