This release is a pre-release and may not be stable for production use.
Recipe for createing a Zope 3 instance
This recipe creates a Zope instance that has been extended by a collection of eggs.
The recipe takes the following options:
- zope3
The name of a section providing a Zope 3 installation definition. This defaults to zope3. The section is required to have a location option giving the location of the installation. This could be a section used to install a part, like a Zope 3 checkout, or simply a section with a location option pointing to an existing install.
- database
The name of a section defining a zconfig option that has a zodb section.
- user
The user name and password for manager user
- eggs
One or more requirements for distributions to be included.
zcml
If specified, provides the list of package ZCML files to include in the instance’s package includes and their order.
By default, the ZCML files normally included in package-includes are ommitted. To includes these, include ‘*’ in the list of includes.
Each entry is a package name with an optional include type and file name. An package name can be optionally followed by a ‘:’ and a file name within the package. The default file name is configure.zcml. The string ‘-meta’ can be included between the file name and the package name. If so, then the default file name is meta.zcml and the include will be treated as a meta include. Similarly for ‘-overrides’. For example, the include:
foo.barCauses the file named NNN-foo.bar-configure.zcml to be inserted into package-includes containing:
<include package=”foo.bar” file=”configure.zcml” />
where NNN is a 3-digit number computed from the order if the entry in the zcml option.
The include:
foo.bar-meta
Causes the file named NNN-foo.bar-meta.zcml to be inserted into package-includes containing:
<include package=”foo.bar” file=”meta.zcml” />
The include:
foo.bar-overrides:x.zcml
Causes the file named NNN-foo.bar-overrides.zcml to be inserted into package-includes containing:
<include package=”foo.bar” file=”x.zcml” />
To do
Need tests
Hopefully, for Zope 3.4, we’ll be able to make the instance-creation process more modular, which will allow a cleaner implementation for this recipe.
Support for multiple storages
Support for more configuration options.
Metadata
Release files for zc.recipe.zope3instance 1.0.0a1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zc.recipe.zope3instance-1.0.0a1-py2.4.egg | Legacy Egg format | - | - | Details for zc.recipe.zope3instance-1.0.0a1-py2.4.egg |
Release files / zc.recipe.zope3instance-1.0.0a1-py2.4.egg
| Download URL | zc.recipe.zope3instance-1.0.0a1-py2.4.egg |
|---|---|
| Size | 7.4 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
7cfad7437b4c3eca4baeea2d515f3962c38ef97e79944e619aeae6c5cc1a8c87
|
|
BLAKE2b-256 checksum How to use checksums |
00cde890e61bfd1ed26970c145ab604858f421e52bdb84a6416149ba89db31eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for zc.recipe.zope3instance 1.0.0a1
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.