On Fri, 30 Sep 2016 10:14:28 +0100 Chris Lamb <la...@debian.org> wrote:
> Neil,
>
> > We're using a gunicorn config
> > in /etc/gunicorn.d/lava-server.gunicorn:
> >
> > CONFIG = {
> > 'mode': 'wsgi',
> > 'working_dir': '/var/lib/lava-server/home/',
> > 'user': 'lavaserver',
> > 'group': 'lavaserver',
> > 'args': (
> > '--bind=127.0.0.1:8000',
> > '--workers=4',
> > '--log-file=/var/log/gunicorn/lava-server.log',
> > '--log-level=debug',
> > 'lava_server.wsgi:application',
> > ),
>
> Due to numerous compatibility and flexibility issues, I took the step
> of removing the cumbersome and error-prone Debian helper from the
> packaging entirely.
OK - should the process just start automatically via apache or similar?
What is the new upstream method for starting gunicorn?
> Whilst regrettable and obviously annoying in the short term, I did
> not want to maintain it for yet another Debian release, further
> distancing ourselves from upstream.
Understandable.
> I am assuming that you upgraded but /etc/init.d/gunicorn file (etc.)
> still exists? I'd love to work with you on getting a cleaner
> Debian-ish but still upstreamable solution if you are up for that? In
> the first instance, may I ask whether you are using systemd?
My test system uses systemd, yes, although I have / can arrange test
VMs with the same lava-server packages with sysVinit as well to cover
those users. Most users will be currently on Jessie and we're looking
to migrate to gunicorn with Stretch, so there will be a lot of users
needing this to work cleanly and without intervention.
Shall we continue updating this closed bug report, create a wishlist
one or move to private email?
--
Neil Williams
=============
http://www.linux.codehelp.co.uk/
pgpc6Nxv66uv5.pgp
Description: OpenPGP digital signature
