Warning
This chapter discusses a model of deployment which is being superceded by the pipeline model. See Setting up a LAVA pipeline instance.
/etc/apache2/sites-available/lava-server.conf
Aimed at apache2.4 with comments for apache2.2 usage. Edit where necessary and then enable and restart apache to use.
lava | meta-package for single instance setup |
lava-server | apache and WSGI settings and HTML content |
lava-dispatcher | dispatches jobs to devices |
The main scheduler daemon is now explicitly named and only restarts the scheduler daemon:
$ sudo service lava-server restart
The web application itself is handled within apache, so to refresh the code running behind the front end, use:
$ sudo apache2ctl restart
The LAVA_SYS_USER has also been renamed from an instance-specific name to lavaserver. lava-server manage can also be run as a normal user or by root. The system user is used just for the filesystem permissions.
https://code.google.com/p/modwsgi/wiki/DebuggingTechniques
If you get a 502 bad gateway, the uwsgi is probably not setup.