comparison development.ini @ 8822:116151b6bfb2

celery: drop tracking of task_id - we use ignore_result=True and will never get anything back There is thus no need for configuration of celery.result_backend . The alternative would be to fix it. That could give better error reporting from failing repo creations, but would require quite a bit of additional changes before it actually works reliably.
author Mads Kiilerich <mads@kiilerich.com>
date Wed, 30 Dec 2020 00:14:57 +0100
parents 0270c714fa17
children fb40978c1afb
comparison
equal deleted inserted replaced
8821:a5c17c93d246 8822:116151b6bfb2
257 ## Celery config settings from https://docs.celeryproject.org/en/4.4.0/userguide/configuration.html prefixed with 'celery.'. 257 ## Celery config settings from https://docs.celeryproject.org/en/4.4.0/userguide/configuration.html prefixed with 'celery.'.
258 258
259 ## Example: use the message queue on the local virtual host 'kallitheavhost' as the RabbitMQ user 'kallithea': 259 ## Example: use the message queue on the local virtual host 'kallitheavhost' as the RabbitMQ user 'kallithea':
260 celery.broker_url = amqp://kallithea:thepassword@localhost:5672/kallitheavhost 260 celery.broker_url = amqp://kallithea:thepassword@localhost:5672/kallitheavhost
261 261
262 celery.result_backend = db+sqlite:///celery-results.db
263
264 #celery.amqp.task.result.expires = 18000
265
266 celery.worker_concurrency = 2 262 celery.worker_concurrency = 2
267 celery.worker_max_tasks_per_child = 100 263 celery.worker_max_tasks_per_child = 100
268 264
269 #################################### 265 ####################################
270 ## BEAKER CACHE ## 266 ## BEAKER CACHE ##