polling a source repository for configuration changes (http, git, s3, etc). When changes are
detected, the new files are retrieved and any locally configured update triggers are executed
(in /etc/repo-deploy/*.d). This is intentionally separate from configuration management systems
like Puppet in order to provide more flexible packaging and build process integration. The
deployer can be configured to run as a daemon (with supervisord) or under cron (or Puppet
agent.)
2 maintainers
Metadata
2 maintainers
Release files for repo-deploy 1.0.8
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 | |
|---|---|---|---|---|
| repo-deploy-1.0.8.tar.gz | 5.9 kB | Without provenance | Details |
Release files / repo-deploy-1.0.8.tar.gz
| Download URL | repo-deploy-1.0.8.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c590bb2589c94598c59d8bcfe768dbf0299f1b737f6120d2c82a75e603e3e5c7
|
|
BLAKE2b-256 checksum How to use checksums |
56f53afd48931316b3b20ccdf2ed94fedff42eca6c3593a1ff14ef9f35e60a49
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for repo-deploy 1.0.8
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.
