djbuild Buildout recipe for Django
Download

djbuild Ranking & Summary

djbuild Tags

Django setup buildout buildout recipe Django setup

djbuild Description

Buildout recipe for Django Based on djangorecipe, the djbuild buildout recipe can be used to create a setup for Django. It will automatically download Django and install it in the buildout's sandbox. You can use either a release version of Django or a subversion checkout (by using trunk instead of a version number).The directory structure is based on: http://django.es/blog/convenciones-proyecto-django/You can see an example of how to use the recipe below:parts = satchmo djangoeggs = ipythonrecipe = gocept.downloadurl = http://www.satchmoproject.com/snapshots/satchmo-0.6.tar.gzmd5sum = 659a4845c1c731be5cfe29bfcc5d14b1recipe = djbuildversion = trunksettings = developmenteggs = ${buildout:eggs}extra-paths = ${satchmo:location}project = dummyshopSupported optionsThe recipe supports the following options.project This option sets the name for your project. The recipe will create a basic structure if the project is not already there.external-apps This option sets the directory where external reusable apps goes. Which do not be installed as an egg or if you don't want install it as an egg.local-apps This option sets the directory where local reusable apps goes, usually put the company name for this directory, and customized apps.projectegg Use this instead of the project option when you want to use an egg as the project. This disables the generation of the project structure.python This option can be used to specify a specific Python version which can be a different version from the one used to run the buildout.version The version argument can accept a few different types of arguments. You can specify trunk. In this case it will do a checkout of the Django trunk. Another option is to specify a release number like 0.96.2. This will download the release tarball. Finally you can specify a full svn url (including the revision number). An example of this would be http://code.djangoproject.com/svn/django/branches/newforms-admin@7833.settings You can set the name of the settings file which is to be used with this option. This is useful if you want to have a different production setup from your development setup. It defaults to development.download-cache Set this to a folder somewhere on you system to speed up installation. The recipe will use this folder as a cache for a downloaded version of Django.extra-paths All paths specified here will be used to extend the default Python path for the bin/* scripts.pth-files Adds paths found from a site .pth file to the extra-paths. Useful for things like Pinax which maintains its own external_libs dir.control-script The name of the script created in the bin folder. This script is the equivalent of the manage.py Django normally creates. By default it uses the name of the section (the part between the ).test If you want a script in the bin folder to run all the tests for a specific set of apps this is the option you would use. Set this to the list of app labels which you want to be tested.testrunner This is the name of the testrunner which will be created. It defaults to test.All following options only have effect when the project specified by the project option has not been created already, on the setting file especified.FCGI specific settingsOptions for FCGI can be set within a settings file (settings.py). The options is FCGI_OPTIONS. It should be set to a dictionary. The part below is an example:FCGI_OPTIONS = { 'method': 'threaded', 'daemonize': 'false',}Another exampleThe next example shows you how to use some more of the options:parts = django extraseggs = hashlibrecipe = iw.recipe.subversionurls = http://django-command-extensions.googlecode.com/svn/trunk/ django-command-extensions http://django-mptt.googlecode.com/svn/trunk/ django-mpttrecipe = djbuildversion = trunksettings = developmentproject = exampleprojectwsgi = trueeggs = ${buildout:eggs}test = someapp anotherappExample using .pth filesPinax uses a .pth file to add a bunch of libraries to its path; we can specify it's directory to get the libraries it specified added to our path:parts = PIL svncode myprojectrecipe = zc.recipe.egg:customegg = PILfind-links = http://dist.repoze.org/recipe = iw.recipe.subversionurls = http://svn.pinaxproject.com/pinax/tags/0.5.1rc1 pinaxrecipe = djbuildversion = 1.0.2eggs = PILproject = myprojectsettings = settingsextra-paths = ${buildout:directory}/myproject/apps ${svncode:location}/pinax/apps/external_apps ${svncode:location}/pinax/apps/local_appspth-files = ${svncode:location}/pinax/libs/external_libswsgi = trueAbove, we use stock Pinax for pth-files and extra-paths paths for apps, and our own project for the path that will be found first in the list. Note that we expect our project to be checked out (e.g., by svn:external) directly under this directory in to 'myproject'.Example with a different Python versionTo use a different Python version from the one that ran buildout in the generated script use something like:parts = myprojectexecutable = /some/special/pythonrecipe = djbuildversion = 1.0.2project = myprojectpython = special-pythonExample configuration for mod_wsgiIf you want to deploy a project using mod_wsgi you could use this example as a starting point:< Directory /path/to/buildout > Order deny,allow Allow from all< /Directory >< VirtualHost 1.2.3.4:80 > ServerName my.rocking.server CustomLog /var/log/apache2/my.rocking.server/access.log combined ErrorLog /var/log/apache2/my.rocking.server/error.log WSGIScriptAlias / /path/to/buildout/bin/django.wsgi< /VirtualHost > Requirements: · Python

djbuild Related Software