Telegraphy
Telegraphy provides real time events for WSGI Python applications with additional features such as event filtering, subscription persistence and authorization/authentication.
It’s initially intended for Django but you can extend it to any WSGI framework.
WebSocket pub/sub and RPC is based on AutobahnPython implementation of WAMP protocol
Getting It
You can get Telegraphy by using pip:
$ pip install telegraphy
You will need to have pip installed on your system. On linux install the python-pip package, on windows follow this. Also, if you are on linux and not working with a virtualenv, remember to use sudo for both commands (sudo pip install telegraphy).
If you want to install it from source, grab the git repository from GitHub and run setup.py:
$ git clone git://github.com/machinalis/telegraphy/telegraphy.git $ cd telegraphy $ python setup.py install
Installing the Django app
Telegraphy’s Django app is installed with the standard procedure: in your projects settings.py file add telegraphy.contrib.django_telegraphy to the INSTALLED_APPS:
INSTALLED_APPS = (
...
'telegraphy.contrib.django_telegraphy',
...
)
Using It
The django_telegraphy app allows you to easily extend your models so that they generate events on creation, update or delete. Those events will reach your front end in real time.
Simply install the django_telegraphy app in your Django project. Then run the following command in parallel to your web-server:
$ python manage.py run_telegraph
Extend your models so that they automatically generate events: create an events.py file next to your models.py
from models import MyModel
from telegraphy.contrib.django_telegraphy.events import BaseEventModel
class MyEventsModel(BaseEventModel):
model = MyModelAnd that’s it! Every time you create, update or delete an instance of your model, an event will reach the frontend.
You can find more examples in the documentation.
More detailed documentation
You can read the docs online here. Or for offline access, you can clone the project code repository and read them from the docs folder.
Help and discussion
For help, suggestions and discussions please refer to http://groups.google.com/group/telegraphy
To guide the development efforts, or if you find any bugs, please use GitHub’s issue tracker.
1 maintainer
Metadata
1 maintainer
Release files for telegraphy 0.1.2.7
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 | |
|---|---|---|---|---|
| telegraphy-0.1.2.7.tar.gz | 52.4 kB | Without provenance | Details |
Release files / telegraphy-0.1.2.7.tar.gz
| Download URL | telegraphy-0.1.2.7.tar.gz |
|---|---|
| Size | 52.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ed68b2dfc82facb6806519645364ad6f66ff21814f6332e620010985648e1b41
|
|
BLAKE2b-256 checksum How to use checksums |
83a730aac16c6180a1e04aeec348f49bc88cdc58cf50afd3a35fb9c8bf54e1c5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for telegraphy 0.1.2.7
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.
