Package: buildout.recipe.uwsgi
buildout.recipe.uwsgiThis is azc.buildoutrecipe for downloading, installing and configuringuWSGIinside a buildout.
It compiles an uWSGI executable inbin/and a configuration file (xmlorini) inparts/.Forked fromshaunsephton.recipe.uwsgi.Changelog0.1.2Change download URL tohttps://.Fixed incorrect working ofis_uwsgi_installed()under Python 3 (issue #29)0.1.1Fixed encoding-related exception when building in an environment without theLANG,LC_*variables set (issue #25)0.1.0Merged some documentation fixesMerged fixes for format strings (python 2.6)0.0.25Added a new configuration optionoutput-formatwhich can be used to specify what kind of configuration file to create
(xml- default, orini)xml-*option have been deprecated in favor ofconfig-*; using the former will cause a warning.0.0.24For the paranoid: Add optionmd5sumto force checksum validation of
downloaded tarball.0.0.23Correctly splitting on ‘\n’ when dealing with multiline options0.0.22Usingsubprocess.check_callfor compatibility with Python 2.60.0.21Check if you need to rebuild uwsgi when updating buildout (which
didn’t work before because update didn’t return the list of
installed paths).Always delete the build directory (even in case of errors).Call uwsgiconfig.py instead of make to install uWSGI. This let you
choose which python you want to use.Check the version of uwsgi if it is already installed.Add an option to configure the path of the generated uWSGI
configuration file.0.0.20Fixed download cache issue; if download-cache is present in the [buildout] section, it will be used for caching the source archive of uwsgi after download0.0.19Setting the PYTHON_BIN env variable to the current python interpreter (for building uwsgi with the right interpreter)0.0.18Fixed issue #110.0.17Add option “pythonpath-eggs-directory” to tweak base directory of generated pythonpath configuration directives0.0.16Documentation enhancements0.0.15Add optiondownload-urlto configure non-vanilla download url0.0.14Extra-paths fixes0.0.13Minor code/documentation cleanups0.0.12Fixed a bug when using ‘use-system-binary’ (was working backwards)Fixed build process when the part’s name was something other than ‘uwsgi’0.0.11New option, use-system-binary, to skip building uwsgi0.0.10Added the version option to allow downloading a specific version ofuwsgiAdded the possibility of specifying a certain build profileOptions that should go in the generated.xmlfile should bexml-prefixedUsageAdd a part to yourbuildout.cfglike this:[buildout]
parts=uwsgi

[uwsgi]
recipe=buildout.recipe.uwsgiRunning the buildout will download and compile uWSGI and add an executable with the same name as your part in thebin/directory (e.g.bin/uwsgi). It will also create auwsgi.xmlconfiguration file in apartsdirectory with the same name as your part (e.g.parts/uwsgi/uwsgi.xml).uwsgican then be started like:$ ./bin/uwsgi --xml parts/uwsgi/uwsgi.xmlBy configuring theoutput-formatoption, you can select other configuration file formats, such asini.Configuration optionsYou can specify a number of options for this recipe, for “fine-tuning” the build process. Below is an example of all possible options that can appear in the buildout file:[buildout]
parts=uwsgi

[uwsgi]
recipe=buildout.recipe.uwsgi
download-url=http://projects.unbit.it/downloads/uwsgi-{0}.tar.gz
version=1.2.5
md5sum=d23ed461d1848aee4cfa16bde247b293
output=${buildout:directory}/parts/uwsgi/uwsgi.ini
output-format=ini
profile=default.ini
use-system-binary=1
config-socket=127.0.0.1:7001
config-module=my_uwsgi_package.wsgi
config-master=Truedownload-urlSpecifies the url where uWSGI’s source code should be downloaded from.{0}inside this url will be replaced by the value of theversionoption. The default value ofdownload-urlishttp://projects.unbit.it/downloads/uwsgi-{0}.tar.gzversionVersion of uWSGI to download (default islatest).md5sumMD5 checksum for the source tarball.  An error will be raised
upon mismatch. If left unset no check is performed.outputPath where the uWSGI configuration file is generated (defaults to a
file called{name of thepart}.{output-format}in the parts directory).output-formatWhat kind of uWSGI configuration file to generate (xmlorini).profileuWSGI has profiles (build configurations) which can be used to configure which plugins will be built with uWSGI (seehttps://github.com/unbit/uwsgi/tree/master/buildconf). Default isdefault.ini. If the specified profile is an absolute path, then that is going to be used, otherwise the profile configuration is searched inuwsgi’s source folder (buildconf/), finally falling back to the current directory (where buildout is invoked from).use-system-binaryIt is possible to use an “external” uwsgi binary (installed by the OS’ package manager or compiled manually) and just let the recipe generate the xml configuration file only (no building uWsgi). Default isFalse.pythonpath-eggs-directoryBy default, the configuration generator will use absolute paths to python eggs, usually insidebuildout:eggs-directoryby callingzc.recipe.egg.Egg(...).working_set().
To support setups which require using the optionrelative-paths= true, this option allows to tweak the base directory of generated uwsgi pythonpath configuration directives, e.g.:pythonpath-eggs-directory = /opt/vendor/product/python/eggsconfig-*Any option starting withconfig-will be stripped of this prefix and written to the configuration file specified byoutput, usingoutput-formatas format; for example,config-socket=127.0.0.1:7001will be output as<socket>127.0.0.1:7001</socket>ifoutput-formatisxml.AuthorsCreated ByShaun SephtonFork MaintainerCosmin LuțălcosminContributorsmooballthefunny42rage2000Andreas MotldavidjbapohJeff DairikiwiseteckBernardo Torres