storagedef
Abstract storage layer
Install
from PyPI:
pip install storagedef
from Source:
pip install -e .
How to use
If you use pyramid:
import storagedef
def main(global_config, **settings):
storage_session = storagedef.Session.from_config(settings, prefix='mystorage.')
config = Configurator(settings=settings)
# Some your configuration using storage_session
return config.make_wsgi_app()
Configuration Keys
Example ini-file if you use ‘mystorage.’ as prefix:
mystorage.engine = storagedef.engines.s3:S3StorageEngine mystorage.credentials_file = ~/.aws/credentials mystorage.config_file = ~/.aws/config mystorage.region = ap-northeast-1 mystorage.bucket = some-test-bucket mystorage.acl = public-read
another ini-file using localmem:
mystorage.engine = storagedef.engines.localmemory:LocalMemoryStorageEngine
Change History
0.1 - 2015-05-09
Initial release.
Metadata
Release files for storagedef 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 |
|---|---|---|---|---|
| storagedef-0.1.tar.gz | 5.5 kB | Without provenance | Details for storagedef-0.1.tar.gz |
Release files / storagedef-0.1.tar.gz
| Download URL | storagedef-0.1.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
abb4c99c79840c41dec333c05a9b034469d606f61e0073ce8d5493548e286c6e
|
|
BLAKE2b-256 checksum How to use checksums |
1d986b212efedb245ae2c80ad9035429c523fe717478cbbe4b9ece92b86163f1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for storagedef 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.