Permabots
CI:
PyPI:
Docs:
Build chat bots and connect then to your app APIs.
With Permabots you can build chat bots and with the same configuration use it for several instant messaging providers. Permabots was born to be a microservice to connect messaging providers to your apps using REST APIs.
Documentation
The full documentation is at https://permabots.readthedocs.org.
Features
Telegram, Kik and Facebook Messenger bots
Message handling definition with regex, as django urls.
HTTP methods: GET/POST/PUT/DELETE/PATCH
Text responses and keyboards with Jinja2 templates
Chat State handling
Asynchronous processing of messages
Media messages not supported
Quickstart
Install permabots:
pip install permabots
Add permabots to your INSTALLED_APPS, and run:
$ python manage.py migrate permabots
Instant messaging providers uses webhooks to send messages to your bots. Add permabots processing urls to your urlpatterns:
url(r'^processing/', include('permabots.urls_processing', namespace="permabots"))
Webhooks are generated with django.contrib.sites. You need it installed and SITE_ID configured. If you want to generate webhook manually you can do it:
MICROBOT_WEBHOOK_DOMAIN = 'https://yourdomain.herokuapp.com'
It is usefull when you don’t have https in your public domain but you have it in your autogenerated domain. i.e. heroku.
Bots are associated to Django Users. You need at least one user, for example admin user.
Then you can create all permabots data, Bots, Conversation Handlers, Notitication Hooks,… via Django admin or with REST API (recommended).
Remember there is an online implementation in www.permabots.com to use it for free.
Demo
You can check and deploy a Permabots demo https://github.com/jlmadurga/permabots-demo
Running Tests
Does the code actually work?
source <YOURVIRTUALENV>/bin/activate (myenv) $ pip install -r requirements/test.txt (myenv) $ make test (myenv) $ make test-all
History
0.1.0 (2016-05-16)
First release on PyPI.
Metadata
Release files for permabots 2.2.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 | Actions |
|---|---|---|---|---|
| permabots-2.2.3.tar.gz | 45.7 kB | Without provenance | Details for permabots-2.2.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| permabots-2.2.3-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for permabots-2.2.3-py2.py3-none-any.whl |
Total release size: 117.2 kB
Release files / permabots-2.2.3.tar.gz
| Download URL | permabots-2.2.3.tar.gz |
|---|---|
| Size | 45.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
38991796c8c794dcf7888404f1e9ca68891c75f302f4327a21a86b7271efc802
|
|
BLAKE2b-256 checksum How to use checksums |
3a41eb3bdf16451b621a27930893d3955cfa347e330f992fa5a3b8b1086ecbdc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / permabots-2.2.3-py2.py3-none-any.whl
| Download URL | permabots-2.2.3-py2.py3-none-any.whl |
|---|---|
| Size | 71.5 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
4e6676a249fbddf7017ca974c409185a3fafd1b12058294e3b844e6b170482d8
|
|
BLAKE2b-256 checksum How to use checksums |
ad385381143a83abee5dfc051618055314231c53cd06ae6c0899217bd6108d0a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for permabots 2.2.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.