summarylogtreecommitdiffstats
path: root/funkwhale-worker.service
diff options
context:
space:
mode:
authorgetzze2019-02-21 23:56:02 +0000
committergetzze2019-02-21 23:56:02 +0000
commit1437585f544174d64166133162ddad60727cf63e (patch)
tree77356cdbfa3cccd4d5507e46731b57e87327fcf5 /funkwhale-worker.service
parenta21fbb5bd1313f3272b457551e1a445b68df50ce (diff)
downloadaur-1437585f544174d64166133162ddad60727cf63e.tar.gz
update to 0.18
Diffstat (limited to 'funkwhale-worker.service')
-rw-r--r--funkwhale-worker.service21
1 files changed, 21 insertions, 0 deletions
diff --git a/funkwhale-worker.service b/funkwhale-worker.service
new file mode 100644
index 000000000000..494b52a02b52
--- /dev/null
+++ b/funkwhale-worker.service
@@ -0,0 +1,21 @@
+[Unit]
+Description=Funkwhale celery worker
+After=redis.service postgresql.service
+PartOf=funkwhale.service
+
+[Service]
+User=funkwhale
+# adapt this depending on the path of your funkwhale installation
+EnvironmentFile=/srv/funkwhale/config/env
+# Celery workers handle background tasks (such file imports or federation
+# messaging). The more processes a worker gets, the more tasks
+# can be processed in parallel. However, more processes also means
+# a bigger memory footprint.
+# By default, a worker will span a number of process equal to your number
+# of CPUs. You can adjust this, by explicitly setting the --concurrency
+# flag:
+# celery -A funkwhale_api.taskapp worker -l INFO --concurrency=4
+ExecStart=/usr/bin/celery -A funkwhale_api.taskapp worker -l INFO --workdir=/usr/share/webapps/funkwhale/api
+
+[Install]
+WantedBy=multi-user.target