> Neil Williams wrote: > > > > No; it really needs to run as a regular standalone process rather > > > than being managed by a web browser. > […] > > One step at a time .... we have some very old code in lava-server > > until at least 2017, it may not take nicely to switching away from > > apache. > > Hm? I'm not suggesting you need to move away from Apache, merely > pointing out that gunicorn *process* is not handled at all by the web > server (a la mod_php and friends) — you proxy the requests through to > it. :)
> > > this systemd file does allow me to run gunicorn > > I think you forgot to attach it? :) We've both been updating the old bug, attaching it to this reply to the correct bug now... > > $ sudo service lava-server-gunicorn status > > ● lava-server-gunicorn.service - lavaserver > […] > > Active: active (running) since Sat 2016-10-01 02:59:13 BST; 23s > > ago > > \o/ -- Neil Williams ============= http://www.linux.codehelp.co.uk/
lava-server-gunicorn.service
Description: Binary data
pgpM_MmkwN6P0.pgp
Description: OpenPGP digital signature
