Files @ 260a7a01b054
Branch filter:

Location: kallithea/init.d/rhodecode-upstart.conf

Mads Kiilerich
follow Python conventions for boolean values

True and False might be singletons and the "default" values for "boolean"
expressions, but "all" values in Python has a boolean value and should be
evaluated as such. Checking with 'is True' and 'is False' is thus confusing,
error prone and unnessarily complex.

If we anywhere rely and nullable boolean fields from the database layer and
don't want the null value to be treated as False then we should check
explicitly for null with 'is None'.
# rhodecode - run the rhodecode daemon as an upstart job
# Change variables/paths as necessary and place file /etc/init/rhodecode.conf
# start/stop/restart as normal upstart job (ie: $ start rhodecode)

description	"RhodeCode Mercurial Server"
author		"Matt Zuba <matt.zuba@goodwillaz.org"

start on (local-filesystems and runlevel [2345])
stop on runlevel [!2345]

respawn

umask 0022

env PIDFILE=/var/hg/rhodecode/rhodecode.pid
env LOGFILE=/var/hg/rhodecode/log/rhodecode.log
env APPINI=/var/hg/rhodecode/production.ini
env HOME=/var/hg
env USER=hg
env GROUP=hg

exec /var/hg/.virtualenvs/rhodecode/bin/paster serve --user=$USER --group=$GROUP --pid-file=$PIDFILE --log-file=$LOGFILE $APPINI

post-stop script
	rm -f $PIDFILE
end script