fedmsg metadata providers for Fedora Infrastructure’s deployment
fedmsg is a set of tools for knitting together services and webapps into a realtime messaging net. This package contains metadata provider plugins for the primary deployment of that system: Fedora Infrastructure.
If you were to deploy fedmsg at another site, you would like want to write your own module like this one that could provide textual representations of your messages.
Pop into #fedora-apps on freenode if you have questions or comments.
Build Status
Branch |
Status |
|---|---|
master |
|
develop |
Running the Tests
# Create a virtualenv and install deps $ sudo dnf install python-virtualenv libffi-devel $ virtualenv my-env $ source my-env/bin/activate # Install the dependencies $ python setup.py develop # Run the tests $ pip install nose $ $(which nosetests)
Building the Docs
# Install additional dependencies $ pip install -r doc/requirements.txt $ sphinx-build doc/ htmldocs/
Metadata
Release files for fedmsg-meta-fedora-infrastructure 0.31.0
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 | |
|---|---|---|---|---|
| fedmsg_meta_fedora_infrastructure-0.31.0.tar.gz | 415.2 kB | Without provenance | Details |
Release files / fedmsg_meta_fedora_infrastructure-0.31.0.tar.gz
| Download URL | fedmsg_meta_fedora_infrastructure-0.31.0.tar.gz |
|---|---|
| Size | 415.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b7f8fad4317d4e78c10a4efc5783efa64cd6c358933d569a16135ebe92e86e35
|
|
BLAKE2b-256 checksum How to use checksums |
ef556748ef499bcca6c2f175d4fc3fdf43932e091ebc75b1d1233b4d2335bf0b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.50.2 CPython/3.8.7
|
Security for fedmsg-meta-fedora-infrastructure 0.31.0
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.