YamJam
keeping private data out of source control and applying DRY principles for resource information since 2009
YamJam is a multi-project, shared, yaml based configuration system. It is also a mechanism to keep secret/private data from leaking out to source control systems (i.e. git, bitbucket, svn, et al) by factoring out sensitive data from your commits.
Factor out sensitive data from your Django settings.py file
Makes install by source control easy by allowing different configs on your dev, staging and production machines
Don’t Repeat Yourself (DRY) Resource configuration
Tested on Python 2.7, 3.2, 3.3, 3.4
Installation
pip install yamjam mkdir ~/.yamjam touch ~/.yamjam/config.yaml chmod -R go-rwx ~/.yamjam
What Next?
License: BSD
We work so well with Django, you’d think we should spell our name YamDjam
1 maintainer
Metadata
1 maintainer
Release files for yamjam 0.1.7
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 |
|---|---|---|---|---|
| yamjam-0.1.7.tar.gz | 4.1 kB | Without provenance | Details for yamjam-0.1.7.tar.gz |
Release files / yamjam-0.1.7.tar.gz
| Download URL | yamjam-0.1.7.tar.gz |
|---|---|
| Size | 4.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
48130b6b5bf38c0931757d6cfde08d0c099e578730267dbae03ee8c2287354e6
|
|
BLAKE2b-256 checksum How to use checksums |
8f2811a0850fc493b9c8670d3e252b1323838771d8f5a2b85d630928249058ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for yamjam 0.1.7
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.
