changeset 8263:f450318e5ff9

celery: change ini template to use sqlite for results 'amqp://' might be good - also for results, but seems to need additional non-trivial setup. And according to https://docs.celeryproject.org/en/3.0/whatsnew-4.0.html#features-removed-for-lack-of-funding it is deprecated. Kallithea only uses Celery results when repos are created or forked and user browsers are reloading pages to poll for completion. amqp seems like unnecessary complexity for that use case. Sqlite does however seem like a minimal but fine solution for the Kallithea use case in most setups.
author Mads Kiilerich <mads@kiilerich.com>
date Fri, 14 Feb 2020 02:25:00 +0100
parents 66670aff96c5
children 09a317dfa793
files development.ini kallithea/lib/paster_commands/template.ini.mako
diffstat 2 files changed, 2 insertions(+), 2 deletions(-) [+]
line wrap: on
line diff
--- a/development.ini	Tue Feb 18 17:03:09 2020 +0100
+++ b/development.ini	Fri Feb 14 02:25:00 2020 +0100
@@ -255,7 +255,7 @@
 ## Example: connect to the virtual host 'rabbitmqhost' on localhost as rabbitmq:
 broker.url = amqp://rabbitmq:qewqew@localhost:5672/rabbitmqhost
 
-celery.result.backend = amqp://
+celery.result.backend = db+sqlite:///celery-results.db
 
 #celery.send.task.error.emails = true
 #celery.amqp.task.result.expires = 18000
--- a/kallithea/lib/paster_commands/template.ini.mako	Tue Feb 18 17:03:09 2020 +0100
+++ b/kallithea/lib/paster_commands/template.ini.mako	Fri Feb 14 02:25:00 2020 +0100
@@ -361,7 +361,7 @@
 <%text>## Example: connect to the virtual host 'rabbitmqhost' on localhost as rabbitmq:</%text>
 broker.url = amqp://rabbitmq:qewqew@localhost:5672/rabbitmqhost
 
-celery.result.backend = amqp://
+celery.result.backend = db+sqlite:///celery-results.db
 
 #celery.send.task.error.emails = true
 #celery.amqp.task.result.expires = 18000