From 55599f3cb52135d6c7ddef3921f434e481be5379 Mon Sep 17 00:00:00 2001 From: Helena Rasche Date: Mon, 4 Nov 2024 12:36:45 +0100 Subject: [PATCH] QKPLOs --- topics/admin/tutorials/celeryless/tutorial.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/topics/admin/tutorials/celeryless/tutorial.md b/topics/admin/tutorials/celeryless/tutorial.md index 670fd5d7e58118..68637121acea81 100644 --- a/topics/admin/tutorials/celeryless/tutorial.md +++ b/topics/admin/tutorials/celeryless/tutorial.md @@ -4,10 +4,14 @@ layout: tutorial_hands_on title: "Alternative Celery Deployment for Galaxy" zenodo_link: "" questions: + - What is *required* for Celery to work in Galaxy? objectives: - Setup the bare minimum configuration to get tasks working + - Avoid deploying, securing, and managing RabbitMQ and Redis and Flower time_estimation: "1h" key_points: + - While a combination of RabbitMQ and Redis is perhaps the most production ready, you can use Postgres as a backend for Celery + - This significantly simplifies operational complexity, and reduces the attack surface of your Galaxy. contributions: authorship: - hexylena @@ -17,7 +21,6 @@ requirements: tutorials: - ansible - ansible-galaxy - - pulsar subtopic: data tags: - ansible