# HG changeset patch
# User Mads Kiilerich <mads@kiilerich.com>
# Date 1581643500 -3600
# Node ID f450318e5ff962d17d6201e32091a2c731aca6d6
# Parent  66670aff96c534f34da60b6cd75ef5b44267fca4
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.

diff -r 66670aff96c5 -r f450318e5ff9 development.ini
--- 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
diff -r 66670aff96c5 -r f450318e5ff9 kallithea/lib/paster_commands/template.ini.mako
--- 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