From ddc8d76a60d777bfd4c71d55c0e26f184f50ea8d Mon Sep 17 00:00:00 2001 From: Helena Rasche Date: Mon, 4 Nov 2024 12:34:34 +0100 Subject: [PATCH] note --- faqs/galaxy/collections_change_datatype.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/faqs/galaxy/collections_change_datatype.md b/faqs/galaxy/collections_change_datatype.md index 8cc7ad7d8df0ce..770f05ac861018 100644 --- a/faqs/galaxy/collections_change_datatype.md +++ b/faqs/galaxy/collections_change_datatype.md @@ -19,4 +19,4 @@ contributors: [shiltemann, hexylena] If you are on a smaller Galaxy server, i.e. not one of the large (multi)national public servers, you may not be able to find this operation, and there is no indication it is missing or why it is disabled. Galaxy has recently started putting [more features behind a setting and deployment configuration](https://docs.galaxyproject.org/en/master/admin/production.html#use-celery-for-asynchronous-tasks) that needs to be enabled by the server administrator. -Your administrator will need to deploy Celery and potentially additionally flower and redis to their stack to enable changing the datatype of a collection. Consider sending them also the link to the [GTN tutorial for setting up redis and flower]({% link topics/admin/tutorials/celery/tutorial.md %}). +Your administrator will need to deploy Celery and potentially additionally flower and redis to their stack to enable changing the datatype of a collection. Consider sending your Galaxy administrator the link to the [simpler deployment option]({% link topics/admin/tutorials/celeryless/tutorial.md %}) or more complex [GTN tutorial for setting up redis and flower]({% link topics/admin/tutorials/celery/tutorial.md %}).