Mercurial > kallithea
view init.d/kallithea-upstart.conf @ 8263:f450318e5ff9
celery: change ini template to use sqlite for results
'amqp://' might be good - also for results, but seems to need additional
non-trivial setup. And according to
https://docs.celeryproject.org/en/3.0/whatsnew-4.0.html#features-removed-for-lack-of-funding
it is deprecated.
Kallithea only uses Celery results when repos are created or forked and user
browsers are reloading pages to poll for completion. amqp seems like
unnecessary complexity for that use case.
Sqlite does however seem like a minimal but fine solution for the Kallithea use
case in most setups.
| author | Mads Kiilerich <mads@kiilerich.com> |
|---|---|
| date | Fri, 14 Feb 2020 02:25:00 +0100 |
| parents | 2c3d30095d5e |
| children |
line wrap: on
line source
# 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