missing documentation on how to install extensions

[Antonio Terceiro]

Trying to follow http://lava-server.readthedocs.org/en/latest/extending.html I did the following:

. /srv/lava/instances/development/bin/activate
cd /path/to/lava-server/demo
./setup.py develop

It blew up with:

~/demo$ ./setup.py develop
error in lava-server-demo setup command: Unable to import 'demo_app': No module named demo_app

I noticed that in the instance virtualenv, '.' is not the load path, so the only way I could install the demo app was with the following patch to setup.py:

----------------8<----------------8<----------------8<-----------------
--- /vagrant/lava-server/trunk/demo/setup.py 2012-12-03 13:37:58.722090000 +0000
+++ setup.py 2013-02-05 18:44:27.926303586 +0000
@@ -20,6 +20,9 @@

 from setuptools import setup, find_packages

+import sys
+sys.path.insert(0, '.')
+

 setup(
     name='lava-server-demo',
----------------8<----------------8<----------------8<-----------------

This feels like a hack that could be avoided if the proper way to install extensions is documented.

[Antonio Terceiro (terceiro)]

properly formatted patch: http://paste.ubuntu.com/1613711/

[Antonio Terceiro (terceiro)]

if a try instead:

$ lava-develop-local /path/to/lava-server-demo

everything seems fines, but then it does not work at all. i.e. no "Demo" link at the top menu, nothing.

[Michael Hudson-Doyle (mwhudson)]

Ah, so sorry that this isn't documented properly. One of the things about buildout is that it separates the packages that are available -- which is what lava-develop-local manipulates -- and which packages are *used* -- this is specified by the value of the 'eggs' entry in the [server] section of the buildout config (plus the dependencies of those packages). So to install a custom extension, you need a custom buildout.cfg, somewhat like what is explained here: http://lava-deployment-tool.readthedocs.org/en/latest/#limited-deployments (except with += rather than -=)

[Antonio Terceiro (terceiro)]

FTR I could make it work here like this:

$ cat /srv/lava/instances/limited/buildout-custom.cfg
[buildout]
extends = buildout-development.cfg

[server]
eggs += lava-server-demo

[branches]
lava-server-demo = /home/vagrant/demo
$ grep BUILDOUT /srv/lava/instances/limited/instance.conf
LAVA_BUILDOUT_CFG='../../buildout-custom.cfg'

[Antonio Terceiro (terceiro)]

FIXED set of commands

for completeness:

for that setup to work /home/vagrant/demo must be a proper bzr repo

I copied the "demo" directory to /home/vagrant/demo, then

cd /home/vagrant/demo
bzr init
bar add .
bzr commit -m 'demo extension'

[Antonio Terceiro (terceiro)]

there is still a typo on comment #6, where it says "bar", it's actually "bzr"

[Tyler Baker (tyler-baker)]

Let try to work on this for 2013.07.