Mercurial > kallithea

view init.d/celeryd-upstart.conf @ 8268:f8f50d3b6512

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
celery: upgrade to Celery 4 Celery 3 doesn't support Python 3.7 or later. This upgrade is thus essential for full Python 3 support. But note that https://docs.celeryproject.org/en/4.4.0/faq.html#does-celery-support-windows says "No". The names of config settings changed in Celery 3 to 4, as described on https://docs.celeryproject.org/en/3.0/whatsnew-4.0.html#lowercase-setting-names . Celery 4 config settings can now be specified in Kallithea .ini files by prefixing with `celery.` - for example as `celery.broker_url`. Remain backwards compatible for the usual settings, and map old names to the new names.
author Mads Kiilerich <mads@kiilerich.com>
date Thu, 20 Feb 2020 02:03:24 +0100
parents 1d539bb18165
children
line wrap: on
line source

# celeryd - run the celeryd daemon as an upstart job for kallithea
# Change variables/paths as necessary and place file /etc/init/celeryd.conf
# start/stop/restart as normal upstart job (ie: $ start celeryd)

description     "Celery for Kallithea Mercurial Server"
author          "Matt Zuba <matt.zuba@goodwillaz.org"

start on starting kallithea
stop on stopped kallithea

respawn

umask 0022

env PIDFILE=/tmp/celeryd.pid
env APPINI=/var/hg/kallithea/production.ini
env HOME=/var/hg
env USER=hg
# To use group (if different from user), you must edit sudoers file and change
# root's entry from (ALL) to (ALL:ALL)
# env GROUP=hg

script
    COMMAND="/var/hg/.virtualenvs/kallithea/bin/kallithea-cli celery-run -c $APPINI -- --pidfile=$PIDFILE"
    if [ -z "$GROUP" ]; then
        exec sudo -u $USER $COMMAND
    else
        exec sudo -u $USER -g $GROUP $COMMAND
    fi
end script

post-stop script
    rm -f $PIDFILE
end script