Mercurial > kallithea
view init.d/celeryd-upstart.conf @ 8352:7dbdb498f460
uwsgi: slim down and tweak the default '[uwsgi]' configuration section
The goal is to have a basic working setup that show how and why to use uWSGI.
System administrators should check uWSGI documentation for further information
and general advice about operations.
Based on uWSGI documentation, experiments, and
https://www.techatbloomberg.com/blog/configuring-uwsgi-production-deployment/ .
author | Mads Kiilerich <mads@kiilerich.com> |
---|---|
date | Sun, 05 Apr 2020 17:09:45 +0200 |
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