collective.recipe.database_url
Use dj-database-url to parse DATABASE_URL for Buildout environments
[buildout]
develop = .
extends =
https://raw.githubusercontent.com/plock/pins/master/plone-4-3
https://raw.githubusercontent.com/plock/pins/master/dev
# https://raw.githubusercontent.com/plock/pins/master/relstorage
# https://raw.githubusercontent.com/plock/pins/master/relstorage
[plone]
eggs +=
RelStorage
psycopg2
parts += database_url
rel-storage =
dbname ${database_url:name}
host ${database_url:host}
type ${database_url:engine}
user ${database_url:user}
password ${database_url:password}
[database_url]
recipe = collective.recipe.database_url
Changelog
0.0.2 (2015-07-04)
Update documentation
0.0.1 (2015-07-03)
Initial release
1 maintainer
Metadata
1 maintainer
Release files for collective.recipe.database_url 0.0.2
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 | |
|---|---|---|---|---|
| collective.recipe.database_url-0.0.2.zip | 11.3 kB | Without provenance | Details |
Release files / collective.recipe.database_url-0.0.2.zip
| Download URL | collective.recipe.database_url-0.0.2.zip |
|---|---|
| Size | 11.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c30645c2e5189a99ffd66613c597cf315b0307d634d4dfed9bbf1739dc0a08bd
|
|
BLAKE2b-256 checksum How to use checksums |
57d74d2f5ef7a6c3c463fe8f182c330718bffbe71a6804272a7b4d5150bcd6d7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.recipe.database_url 0.0.2
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.
