Mercurial > kallithea
view init.d/celeryd-upstart.conf @ 3733:af049a957506 beta
fixed default permissions population during upgrades
- it often happen that introducing new permission
caused default permission to reset it's state to installation
default.
new version makes sure that only missing permissions are
created while leaving old defaults
author | Marcin Kuzminski <marcin@python-works.com> |
---|---|
date | Wed, 10 Apr 2013 02:55:21 +0200 |
parents | 58df0b3ed377 |
children | 99ad9d0af1a3 |
line wrap: on
line source
# celeryd - run the celeryd daemon as an upstart job for rhodecode # 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 RhodeCode Mercurial Server" author "Matt Zuba <matt.zuba@goodwillaz.org" start on starting rhodecode stop on stopped rhodecode respawn umask 0022 env PIDFILE=/tmp/celeryd.pid env APPINI=/var/hg/rhodecode/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/rhodecode/bin/paster celeryd $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