Neuigkeiten
Die 10 wichtigsten IT-Technologien 2010
16 Nov 2009 von friedel
Snowsprint 2010 - Registrierung geöffnet
29 Sep 2009 von Manfred Schwendinger
Using buildout with appengine
21 Sep 2009 von Bernd Dorn
Internet Explorer 6 - Time To Say Goodbye!
27 Aug 2009 von Manfred Schwendinger
Europython Birmingham 2009 - Ein Rückblick
30 Jul 2009 von Manfred Schwendinger
Lovely Systems bei EuroPython 2009
25 Jun 2009 von Andreas Feuerstein
Manunia Friedel übernimmt Business Relations
29 Mai 2009 von Andreas Feuerstein
Neue Version von a-z.ch ist online!
06 Apr 2009 von Andreas Feuerstein
Jodok ist Chief Technical Officer von studiVZ
02 Apr 2009 von Andreas Feuerstein
Zehn.de gewinnt VisionAward_09
16 März 2009 von Andreas Feuerstein
Manfred gibt Cloud Computing Talk bei CeBIT
05 März 2009 von Andreas Feuerstein
DLD09 - Cloud Computing in der Praxis
18 Feb 2009 von Andreas Feuerstein
zoomer.de geht vom Netz
11 Feb 2009 von Andreas Feuerstein
Jodok am Cloud Computing Podium bei DLD09
26 Jan 2009 von Andreas Feuerstein
Zehn.de schwebt auf der Wolke!
10 Dez 2008 von Andreas Feuerstein
Lovely Systems ist nun eine AG!
26 Nov 2008 von Ewald Natter
7. Internationale Semantic Web Konferenz
28 Okt 2008 von Andreas Feuerstein
Snow-Sprint Sponsoren





Lovely Twitter
Using buildout with appengine
21 Sep 2009 von Bernd Dorn, gepostet in cloud, Python und Web (2.0)
At Lovely Systems we use zc.buildout to configure our appengine projects. With this post we'd like to introduce one method where buildout could be used for an appengine application that depends on 3rd party modules. In this example the tornado modules are used for views and zope.testing and webtest for testing.

The example application is part of the lovely-gae package. The source can be browsed here and the running application is available at http://lovely-gae.appspot.com/ (there is not much to see).

To run the app you just have to export/checkout the example app directory.

svn export https://lovely-gae.googlecode.com/svn/trunk/example

Then replace the application id with your application id in
app/app.yaml

Now run the bootstrap script, which downloads setuptools and buildout, and creates the buildout commandline tool in bin/buildout.

python bootstrap.py

Now you have to run the actual buildout.

./bin/buildout

This creates a ./bin/instance executable that starts the development server. Note that the dev_appserver.py script from the appengine SDK has to be on the path in order for this to work.

Now to start the development server run

./bin/instance

and go to http://localhost:8080 with your browser to view the start page.

Take a look at the following files, which are all documented inline:

buildout.cfg
app/app.yaml
app/environment.py
app/main.py
app/tests.py


Tests can be run by using the generated ./bin/test executable. Run it with the --help option to get more information.

Caveats

Currently the egg directory is not cleaned up when a newer version of an egg is available, so the app/packages directory needs to be deleted and the bootstrap buildout process has to be re-run, so that the old packages are not in the python path anymore.