Introduction
‘’collective.recipe.modwsgi’’ is a zc.buildout recipe which creates a paste.deploy entry point for mod_wsgi.
It is very simple to use. This is a minimal ‘’buildout.cfg’’ file which creates a WSGI script mod_python can use:
[buildout]
parts = mywsgiapp
[mywsgiapp]
recipe = collective.recipe.modwsgi
eggs = mywsgiapp
config-file = ${buildout:directory}/production.ini
This will create a small python script in parts/mywsgiapp called ‘’wsgi’’ which mod_wsgi can load. You can also use the optional ‘’extra-paths’’ option to specify extra paths that are added to the python system path.
The apache configuration for this buildout looks like this::
WSGIScriptAlias /mysite /home/me/buildout/parts/mywsgiapp/wsgi
<Directory /home/me/buildout>
Order deny,allow
Allow from all
</Directory>
This recipe does not fully install packages, which means that console scripts will not be created. If you need console scripts you can add a second buildout part which uses z3c.recipe.scripts to do a full install.
Changelog
1.3 - January 13, 2012
Gracefully handle .ini files that do not contain logging configuration. [wichert]
don’t overwrite existing file permissions when setting execute permission. This fixes issue 1 [fredj]
1.2 - August 7, 2009
Initialise the python logging module. Based on a patch from Philip Kershaw, which was based on a discussion on pylons-discuss: http://groups.google.com/group/pylons-discuss/browse_thread/thread/9b9add4529b3779c?pli=1 [wichert]
1.1 - April 20, 2009
Add an ‘extra-paths’ option, similar the the zc.recipe.egg one. [chrism]
1.0 - October 16, 2008
No changes. [wichert]
1.0rc1 - June 30, 2008
Update the generated wrapper to test if a path is already in sys.path before adding it. This prevents paths being duplicated in sys.path when mod_wsgi reloads the module. [wichert]
1.0b3 - June 23, 2008
Do not make the recipe a subclass of zc.recipe.egg.Eggs but use a local instance to determine the working set. [wichert]
Format the sys.path changes in the wrapper to make it more human readable. This is purely cosmetic to help with debugging. [wichert]
Also recreate the wsgi wrapper file when updating a buildout part. This is needed to get get changes to versions in the working set (such as different version pins) reflected in the wrapper. [wichert]
1.0b2 - June 13, 2008
Call the Eggs constructor as well: working_set() needs too many of the internal variables it sets for us to set them ourselves. This fixes the recipe breaking when using find-links in buildout. [wichert]
1.0b1 - June 13, 2008
Initial release [wichert]
1 maintainer
Metadata
1 maintainer
Release files for collective.recipe.modwsgi 1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| collective.recipe.modwsgi-1.3.tar.gz | 4.2 kB | Without provenance | Details for collective.recipe.modwsgi-1.3.tar.gz |
Release files / collective.recipe.modwsgi-1.3.tar.gz
| Download URL | collective.recipe.modwsgi-1.3.tar.gz |
|---|---|
| Size | 4.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c1c2f7959e85e784fea5f99541a355a3f4cbc4fca326b85c9d85ecbca32a52e0
|
|
BLAKE2b-256 checksum How to use checksums |
564a4ae58248abde07065830b07072adc1ef7a90fd63b6e52bca9871937aefdd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.recipe.modwsgi 1.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
