Detailed Documentation
This recipe use plone.recipe.zope2instance and plone.recipe.zope2zeoserver to generate config files and instances for Zope2 instances / zeo server using repoze.zope2
This mean that you intances are wsgi applications served by PasteDeploy.
WSGI Instance
Recipe options are the same than plone.recipe.zope2instance.
The default logging config is override to log to STDERR instead of standard log files. You can change this by setting event-log-custom and access-log-custom options.
We’ll start by creating a buildout that uses the recipe:
>>> write('buildout.cfg',
... """
... [buildout]
... parts = instance
... extends =
... http://dist.plone.org/release/3.3/versions.cfg
... http://download.zope.org/zope3.4/3.4.0/versions.cfg
... find-links =
... http://dist.repoze.org/zope2/2.10/
... versions = versions
...
... [instance]
... recipe = collective.recipe.zope2wsgi
... user = admin:admin
... """)
Running the buildout gives us:
>>> print 'start', system(buildout) start Installing instance. Generated config file '/sample-buildout/instance.ini' Generated script '/sample-buildout/bin/instance'. Generated script '/sample-buildout/bin/instance.wsgi'.
Then you just need to run:
$ bin/instance serve
This will launch the application with Paste with the generated instance.ini file.
You can also use mod_wsgi with the instance.wsgi script (this is not tested but should work).
Using ZEO
Recipe options are the same than plone.recipe.zope2zeoserver.
We’ll start by creating a buildout that uses the recipe:
>>> write('buildout.cfg',
... """
... [buildout]
... parts = zeo instance
... extends =
... http://dist.plone.org/release/3.3/versions.cfg
... http://download.zope.org/zope3.4/3.4.0/versions.cfg
... find-links =
... http://dist.repoze.org/zope2/2.10/
... versions = versions
...
... [zeo]
... recipe = collective.recipe.zope2wsgi:zeo
...
... [instance]
... recipe = collective.recipe.zope2wsgi
... user = admin:admin
... zeo-client = on
... """)
Running the buildout gives us:
>>> print 'start', system(buildout) start ... Installing zeo. Created directory /sample-buildout/parts/zeo ... Generated script '/sample-buildout/bin/zeo'. Generated script '/sample-buildout/bin/zeopack'. Installing instance. Generated script '/sample-buildout/bin/instance'. Generated script '/sample-buildout/bin/instance.wsgi'.
Then you just need to run:
$ bin/zeo start $ bin/instance serve --daemon
Contributors
Gael Pasgrimaud <gael@gawel.org>
Change history
0.1 (2009-09-04)
Initial release [gawel]
Download
Metadata
Release files for collective.recipe.zope2wsgi 0.1
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.zope2wsgi-0.1.tar.gz | 200.1 kB | Without provenance | Details for collective.recipe.zope2wsgi-0.1.tar.gz |
Release files / collective.recipe.zope2wsgi-0.1.tar.gz
| Download URL | collective.recipe.zope2wsgi-0.1.tar.gz |
|---|---|
| Size | 200.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ed2616b53efb9c21fa98726a8cdecc3a59d61cfb1683a0a28cca7ff8da5e707f
|
|
BLAKE2b-256 checksum How to use checksums |
1222f80faa3ebe96b4d30b1504b14010819b973221057f9de6fd3fa8be4b4fd7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.recipe.zope2wsgi 0.1
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.