Installation
devpi-slack needs to be installed alongside devpi-server.
You can install it with:
pip install devpi-slack
For devpi-server there is no configuration needed, as it will automatically discover the plugin through calling hooks using the setuptools entry points mechanism.
Details about configuration below.
Configuration
devpi-slack can trigger Slack notifications upon package upload.
devpi index /testuser/dev slack_icon=http://doc.devpi.net/latest/_static/devpicat.jpg slack_hook=https://hooks.slack.com/services/XXX/YYY/ZZZ slack_user=devpi
Environment Variables:
Optionally, you can pass environment variables to configure the plugin.
SLACK_HOOK to adjust the Slack hook URL used. Defaults to the devpi slack_hook value above. (Note: slack_hook provided by devpi takes precedence. Setting both will default to the value specified in devpi)
SLACK_ICON to adjust the Slack icon used. Defaults to: <http://doc.devpi.net/latest/_static/devpicat.jpg>
SLACK_USER to adjust the Slack username used. Defaults to: devpi
Uninstall
Remove the index configuration:
devpi index /testuser/dev slack_icon-= slack_hook-= slack_user-=
1 maintainer
Metadata
1 maintainer
Release files for devpi-slack 0.1.4
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 | |
|---|---|---|---|---|
| devpi-slack-0.1.4.tar.gz | 3.5 kB | Without provenance | Details |
Release files / devpi-slack-0.1.4.tar.gz
| Download URL | devpi-slack-0.1.4.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f586603aa21058002eb0a44711b397514a39a1d381f1364efdfec42679d0d92d
|
|
BLAKE2b-256 checksum How to use checksums |
7aaa34f75acfc328692b1d7f34081c5c932a4efbca47ffc452c17898ea42f483
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/3.7
|
Security for devpi-slack 0.1.4
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.
