======
relay2slack is a tool for capturing and forwarding incoming Slack webhook events.
Installation
------------
To install relay2slack, simply:
.. code-block:: bash
$ pip install relay2slack
To run relay2slack in the foreground:
.. code-block:: bash
$ relay2slack
If you would like to daemonize relay2slack, refer to `docs/ <docs/>`_ for supported methods.
Usage
-----
For whichever service you would like to product webhook events, instead point it to http://localhost:5000/relay with the normal JSON object you expect to send to Slack. For example:
.. code-block:: bash
curl -X POST -d 'payload={"channel":"@blaketmiller","username":"My service","icon_emoji":":warning:","text":"Hello world"}' http://localhost:5000/relay
relay2slack receives that request and forwards the posted JSON object onto the actual Slack webhook endpoint that you provide it in `SLACK_TOKEN`.
1 maintainer
Metadata
1 maintainer
Release files for relay2slack 0.3
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 | |
|---|---|---|---|---|
| relay2slack-0.3.tar.gz | 2.3 kB | Without provenance | Details |
Release files / relay2slack-0.3.tar.gz
| Download URL | relay2slack-0.3.tar.gz |
|---|---|
| Size | 2.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9b4275a5c89a4078d9ab6d2b50c7d1c42d6255962d1b404cd51d3f1de1db4937
|
|
BLAKE2b-256 checksum How to use checksums |
ff9c029540267a71b3056498bf12808a24db3ca103959dea50ee10c984e12fa4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for relay2slack 0.3
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.
