This release is a pre-release and may not be stable for production use.
What is iw.recipe.fss ?
This recipe configure FSS Storage.
How to use iw.recipe.fss ?
The recipe is called by buildout, let’s create an instance of it, with a buildout simulated context:
>>> import os
>>> data_dir = os.path.join(test_dir, 'data')
>>> bin_dir = os.path.join(data_dir, 'bin')
>>> var_dir = os.path.join(data_dir, 'var2')
>>> conf_dir = os.path.join(data_dir, 'etc')
>>> buildout = {'instance': {'location': data_dir},
... 'buildout': {'bin-directory': bin_dir}}
>>> name = 'fss'
>>> options = {'conf': os.path.join(conf_dir,
... 'plone-filesystemstorage.conf'),
... 'storages': """
... storage1 /site/storage1
... storage2 /site/storage2 flat
... storage2 /site/storage2 flat %s/storage %s/backup
... """ % (var_dir, var_dir)}
Creating the recipe:
>>> from iw.recipe.fss import Recipe >>> recipe = Recipe(buildout, name, options)
Running it:
>>> paths = list(recipe.install())
Checking files created:
>>> paths.sort() >>> paths ['...data/etc/plone-filesystemstorage.conf', '...data/var/fss_backup_storage1', '...data/var/fss_backup_storage2', '...data/var/fss_storage_storage1', '...data/var/fss_storage_storage2', '...data/var2/backup', '...data/var2/storage']
Checking the conf file:
>>> conf = open(os.path.join(conf_dir, ... 'plone-filesystemstorage.conf')) >>> print conf.read() # FSS conf file generated by iw.recipe.fss <BLANKLINE> <BLANKLINE> # storage storage1 <site /site/storage1> storage-path /.../data/var/fss_storage_storage1 backup-path ...data/var/fss_backup_storage1 storage-strategy directory </site> <BLANKLINE> # storage storage2 <site /site/storage2> storage-path ...data/var/fss_storage_storage2 backup-path ...data/var/fss_backup_storage2 storage-strategy flat </site> <BLANKLINE> # storage storage2 <site /site/storage2> storage-path ...data/var2/storage backup-path ...data/var2/backup storage-strategy flat </site> <BLANKLINE>
Cleaning up the files:
>>> for path in paths: ... try: ... os.rmdir(path) ... except: ... os.remove(path)
Metadata
Release files for iw.recipe.fss 0.1bdev-r6471
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| iw.recipe.fss-0.1bdev_r6471-py2.5.egg | Legacy Egg format | - | - | Details for iw.recipe.fss-0.1bdev_r6471-py2.5.egg |
| iw.recipe.fss-0.1bdev_r6471-py2.4.egg | Legacy Egg format | - | - | Details for iw.recipe.fss-0.1bdev_r6471-py2.4.egg |
Total release size: 21.4 kB
Release files / iw.recipe.fss-0.1bdev_r6471-py2.5.egg
| Download URL | iw.recipe.fss-0.1bdev_r6471-py2.5.egg |
|---|---|
| Size | 10.7 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
da22c52e7be4a1db979169d5e278ade56b44d1ca29d3389e0f2fd1f60a0fb7f4
|
|
BLAKE2b-256 checksum How to use checksums |
4d19c6c77c89076ae1394861ab3790dce3995523665cfe04b01c2f827d06ee84
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / iw.recipe.fss-0.1bdev_r6471-py2.4.egg
| Download URL | iw.recipe.fss-0.1bdev_r6471-py2.4.egg |
|---|---|
| Size | 10.7 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
8515ae8572c1a1e0856200e90017f19857b55f4cf93112d02db8442d3d635b28
|
|
BLAKE2b-256 checksum How to use checksums |
1a2d5527474d76a9c52ceea54d7fa515d9c01ba402f9358a07b1077e46e0af04
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for iw.recipe.fss 0.1bdev-r6471
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.