This release is a pre-release and may not be stable for production use.
Motivation
We’re deploying multiple test/staging servers using django and it’s a pain to have lots of apache confs lying around which are almost exactly the same.
The only things that are different are the IP addresses, server names and, if using buildout (which is kind of the whole point of this), the python path and packages. So a valid approach would be to put your apache conf somewhere under your buildout directory and have it built at the same time as you buildout your project.
There’s already a nice recipe that does this z3c.recipe.filetemplate. So this recipe is subclassing from that and using zc.recipe.egg to add a python_path value to the options. This is done by setting the eggs and extra-paths values in the recipe.
This is just an internal project so there’s no bug tracker, mailing list etc. I hope that someone finds it useful, please contact me it you do or wish to make changes to it.
Download
Metadata
Release files for twodeg.recipe.apacheconf 0.2dev
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 |
|---|---|---|---|---|
| twodeg.recipe.apacheconf-0.2dev.tar.gz | 3.6 kB | Without provenance | Details for twodeg.recipe.apacheconf-0.2dev.tar.gz |
Release files / twodeg.recipe.apacheconf-0.2dev.tar.gz
| Download URL | twodeg.recipe.apacheconf-0.2dev.tar.gz |
|---|---|
| Size | 3.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
58b471765c1fc91ebf2f2d89b23956df6d53350bc6994013c3ad3cfc5cb22831
|
|
BLAKE2b-256 checksum How to use checksums |
4d5d616be9d57346a63e2779ce8ce53b36043d71cdfa3cf07f964ff27bcb5df8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for twodeg.recipe.apacheconf 0.2dev
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.