Files
@ 1c68258b14bc
Branch filter:
Location: kallithea/init.d/kallithea-upstart.conf - annotation
1c68258b14bc
759 B
text/plain
tests: notifications: increase indentation of multi-line for loop condition
Code in question is:
for foo in [
item1,
item2,
item3]:
action1
action2
With the above indentation, a quick glance at the code does not show where
the actions start.
Using a double indentation for line continuation avoids this problem:
for foo in [
item1,
item2,
item3]:
action1
action2
There are no actual code changes in this commit.
Code in question is:
for foo in [
item1,
item2,
item3]:
action1
action2
With the above indentation, a quick glance at the code does not show where
the actions start.
Using a double indentation for line continuation avoids this problem:
for foo in [
item1,
item2,
item3]:
action1
action2
There are no actual code changes in this commit.
99ad9d0af1a3 99ad9d0af1a3 99ad9d0af1a3 99ad9d0af1a3 e285bb7abb28 e285bb7abb28 99ad9d0af1a3 99ad9d0af1a3 99ad9d0af1a3 99ad9d0af1a3 99ad9d0af1a3 99ad9d0af1a3 99ad9d0af1a3 99ad9d0af1a3 99ad9d0af1a3 99ad9d0af1a3 99ad9d0af1a3 99ad9d0af1a3 99ad9d0af1a3 99ad9d0af1a3 99ad9d0af1a3 2c3d30095d5e 99ad9d0af1a3 99ad9d0af1a3 e285bb7abb28 99ad9d0af1a3 | # kallithea - run the kallithea daemon as an upstart job
# Change variables/paths as necessary and place file /etc/init/kallithea.conf
# start/stop/restart as normal upstart job (ie: $ start kallithea)
description "Kallithea 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/kallithea/kallithea.pid
env LOGFILE=/var/hg/kallithea/log/kallithea.log
env APPINI=/var/hg/kallithea/production.ini
env HOME=/var/hg
env USER=hg
env GROUP=hg
exec /var/hg/.virtualenvs/kallithea/bin/gearbox serve --user=$USER --group=$GROUP --pid-file=$PIDFILE --log-file=$LOGFILE -c $APPINI
post-stop script
rm -f $PIDFILE
end script
|