Package: redsolution.djangorecipe
DescriptionThis is the Redsolution’sforkof officialdjangorecipepackage.
Fork created for test compability and to propose changes in official repository.Fork changes:removed django requirement in djangorecipe packageremoved parts/django path from sys.pathOriginal documentation:This 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 see an example of how to use the recipe below:[buildout]
parts = satchmo django
eggs =
  ipython
versions = versions

[versions]
django = 1.2.5


[satchmo]
recipe = gocept.download
url = http://www.satchmoproject.com/snapshots/satchmo-0.6.tar.gz
md5sum = 659a4845c1c731be5cfe29bfcc5d14b1

[django]
recipe = djangorecipe
settings = development
eggs = ${buildout:eggs}
extra-paths =
  ${satchmo:location}
project = dummyshopSupported optionsThe recipe supports the following options.projectThis option sets the name for your project. The recipe will create a
basic structure if the project is not already there.projecteggUse this instead of the project option when you want to use an egg
as the project. This disables the generation of the project
structure.pythonThis option can be used to specify a specific Python version which can be a
different version from the one used to run the buildout.settingsYou 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 todevelopment.extra-pathsAll paths specified here will be used to extend the default Python
path for thebin/*scripts.pth-filesAdds paths found from a site.pthfile to the extra-paths.
Useful for things like Pinax which maintains its own external_libs dir.control-scriptThe name of the script created in the bin folder. This script is the
equivalent of themanage.pyDjango normally creates. By default it
uses the name of the section (the part between the[ ]).wsgiAn extra script is generated in the bin folder when this is set totrue. This can be used with mod_wsgi to deploy the project. The
name of the script iscontrol-script.wsgi.wsgilogIn case the WSGI server you’re using does not allow printing to stdout,
you can set this variable to a filesystem path - all stdout/stderr data
is redirected to the log instead of printedfcgiLikewsgithis creates an extra script within the bin folder. This
script can be used with an FCGI deployment.testIf 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.testrunnerThis is the name of the testrunner which will be created. It
defaults totest.All following options only have effect when the project specified by
the project option has not been created already.urlconfYou can set this to a specific url conf. It will use project.urls by
default.secretThe secret to use for thesettings.py, it generates a random
string by default.FCGI specific settingsOptions for FCGI can be set within a settings file (settings.py). The options
isFCGI_OPTIONS. It should be set to a dictionary. The part below is an
example:FCGI_OPTIONS = {
    'method': 'threaded',
}Another exampleThe next example shows you how to use some more of the options:[buildout]
parts = django extras
eggs =
  hashlib

[extras]
recipe = iw.recipe.subversion
urls =
  http://django-command-extensions.googlecode.com/svn/trunk/ django-command-extensions
  http://django-mptt.googlecode.com/svn/trunk/ django-mptt

[django]
recipe = djangorecipe
settings = development
project = exampleproject
wsgi = true
eggs =
  ${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:[buildout]
parts = PIL
        svncode
        myproject
versions=versions

[versions]
django        = 1.3

[PIL]
recipe        = zc.recipe.egg:custom
egg           = PIL
find-links    = http://dist.repoze.org/

[svncode]
recipe        = iw.recipe.subversion
urls          = http://svn.pinaxproject.com/pinax/tags/0.5.1rc1       pinax

[myproject]
recipe        = djangorecipe
eggs          =
  PIL
project       = myproject
settings      = settings
extra-paths   = ${buildout:directory}/myproject/apps
                ${svncode:location}/pinax/apps/external_apps
                ${svncode:location}/pinax/apps/local_apps
pth-files     = ${svncode:location}/pinax/libs/external_libs
wsgi          = 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:[buildout]
parts = myproject

[special-python]
executable = /some/special/python

[myproject]
recipe        = djangorecipe
project       = myproject
python        = 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>Changes1.1.2Added correct url to the deprecation warning1.1.1Fixed Python3 Trove classifiers1.1Support python3.Changed buildout and the tests to run the tests under nose.Removed some old pre 0.99 unittests that dealt with download support.1.0Stable release with a real 1.0 version.Made djangorecipe more pep08 compliant.0.99Djangorecipe now depends on Django. The use of theversion =statement
is deprecated. Specify the django version in the[versions]section. Install django via mr.developer if you need to use
an svn/git/hg repository. For other uses
Versionpin djangorecipe to 0.23.1 if you don’t want to upgrade.
Thanks to Reinout van Rees for help with this release.Removed subversion and download support.0.23.1Added a missing ‘import os’0.23Support for settings/urls boilerplate for django 1.2 and django 1.3.
It defaults to 1.3 when the version isn’t 1.2.0.22Added support for svn urls with spaces. Thanks to Brad103 (fixes #537718).Updated code and buildout to use newest zc.recipe.egg,
zc.recipe.testrunner and python-dateutil.0.21The admin url is now configured for django 1.1 or higher. Thanks to
Sam Charrington (fixes #672220).Bootstrap.py updated (fixes #501954).0.20The recipe know makes thedjangopackage know to setuptools during install.
This closes #397864. Thanks to Daniel Bruce and Dan Fairs for the patch.Fixed #451065 which fixes a problem with the WSGI log file option.Added the posibilty to configure more FCGI related settings. Thanks to Vasily
Sulatskov for the patch.0.19.2The generated WSGI & FCGI scripts are now properly removed when
options change (fixes #328182). Thanks to Horst Gutmann for the
patch.Scripts are now updated when dependencies change. This fixes #44658,
thanks to Paul Carduner for the patch.0.19.1Applied fix for the change in WSGI script generation. The previous
release did not work properly.0.19When running again with non-newest set the recipe will no longer
update the Subversion checkout. Thanks to vinilios for the patch.The WSGI and FCGI scripts are now generated using Buildout’s own
system. This makes them more similar to the generated manage script
with regard to the setup of paths. Thanks to Jannis Leidel for the
patch.0.18Paths from eggs and extra-paths now get precedence over the default
system path (fixes #370420). Thanks to Horst Gutmann for the patch.The generated WSGI script now uses thepythonoption if
present. This fixes #361695.0.17.4Fixed a problem when not running in verbose mode (fixes #375151).0.17.3Removed dependency on setuptools_bzr since it does not seem to work
like I expected.0.17.2Changed the download code to use urllib2. This should make it work
from behind proxies (fixes #362822). Thanks to pauld for the patch.0.17.1Fixed a problem with the new WSGI logging option #348797. Thanks to
Bertrand Mathieu for the patch.Disable generation of the WSGI log if “wsgilog” isn’t set, thanks to
Jacob Kaplan-Moss for the patch.Updated buildout.cfg and .bzrignore, thanks Jacob Kaplan-Moss.0.17Added an option to specify a log file for output redirection from
the WSGI script. Thanks to Guido Wesdorp for the patch.0.16Subversion aliases are now supported (something like
svn+mystuff://myjunk). Thanks to Remco for the patch.0.15.2Update to move pth-files finder from the __init__ method to the
install method so it runs in buildout-order, else it looks for pth
files in dirs that may not yet exist. Thanks to Chris Shenton for
the update to his original patch.0.15.1Update to make the previously added pth-files option better
documented.0.15Added “pth-files” option to add libraries to extra-paths from
site .pth files. Thanks to Chris Shenton for the patch.0.14The recipe now supports creating a FCGI script. Thanks to Jannis
Leidel for the patch.When downloading a Django recipe for the first time the recipe now
properly reports the url it is downloading from.0.13Specifying a user name within a subversion url now works. The code
that determined the revision has been updated. This fixes issue
#274004. Thanks to Remco for the patch.Updated the template for creating new projects. It now uses the
current admin system when generating it’surls.pyfile. This fixes
issue #276255. Thanks to Roland for the patch.0.12.1Re-upload since CHANGES.txt was missing from the release0.12The recipe no longer executes subversion to determine whether the
versions is to be downloaded using subversion. This fixes issue
#271145. Thanks to Kapil Thangavelu for the patch.Changed thepythonpathoption toextra-paths. This makes the
recipe more consistent with other recipes (see issue #270908).0.11Another go at fixing the updating problem (#250811) by making sure
the update method is always called. It would not be called in the
previous version since the recipe wrote a random secret (if it
wasn’t specified) to the options for use with a template. Buildout
saw this as a change in options and therefore always decided to
un-install & install.When both projectegg and wsgi=True are specified, the generated wsgi
file did not have the correct settings file in it. This has been
fixed with a patch from Dan Fairs.The recipe now has logging. All print statements have been replaced
and a few extra logging calls have been added. This makes the recipe
more informative about long running tasks. Thanks erny for the patch
from issue #260628.0.10The recipe no longer expects the top level directory name in a
release tarball to be consistent with the version number. This fixes
issue #260097. Thanks to erny for reporting this issue and
suggesting a solution.Revision pinns for the svn checkout now stay pinned when re-running
the buildout. This fixes issue #250811. Thanks to Remco for
reporting this.Added an option to specify an egg to use as the project. This
disables the code which creates the basic project structure. Thanks
to Dan Fairs for the patch from issue #252647.0.9.1Fixed the previous release which was broken due to a missing
manifest file0.9The settings option is fixed so that it supports arbitrary depth
settings paths (example;conf.customer.development).The version argument now excepts a full svn url as well. You can use
this to get a branch or fix any url to a specific revision with the
standard svn @ syntaxThe wsgi script is no longer made executable and readable only by
the user who ran buildout. This avoids problems with deployment.