============================================
Python Ripple API and transaction management
============================================
Settings
========
* ``RIPPLE_ACCOUNT`` - account that acts as 'manager' and monitors incoming transactions
* ``RIPPLE_SECRET`` - secret for 'manager' account
* ``RIPPLE_API_DATA[0]['RIPPLE_API_URL']``
* ``RIPPLE_API_DATA[0]['RIPPLE_API_USER']``
* ``RIPPLE_API_DATA[0]['RIPPLE_API_PASSWORD']``
* ``RIPPLE_TIMEOUT`` - timeout for django manamgement command calls
* ``RIPPLE_TRANSACTION_MONITOR_MIN_LEDGER_INDEX`` - offset, ledger index to start transaction monitoring with,
default is the beginning of time
Example Config::
RIPPLE_API_DATA = [
{
'RIPPLE_API_URL': 'http://s_west.ripple.com:51234',
'RIPPLE_API_USER': '',
'RIPPLE_API_PASSWORD': '',
}
] # You can specify multiple servers and ripple_api app will try them in order if one of servers
# returns error
Signals
=======
* ``ripple_api.signals.transaction_status_changed = Signal(providing_args=["old_status"])`` - sent
when existing Transaction's status is changed
* default django's post_save signal is useful to get new Transactions
.. TODO:
* docs on api usage
* docs on management command
Python Ripple API and transaction management
============================================
Settings
========
* ``RIPPLE_ACCOUNT`` - account that acts as 'manager' and monitors incoming transactions
* ``RIPPLE_SECRET`` - secret for 'manager' account
* ``RIPPLE_API_DATA[0]['RIPPLE_API_URL']``
* ``RIPPLE_API_DATA[0]['RIPPLE_API_USER']``
* ``RIPPLE_API_DATA[0]['RIPPLE_API_PASSWORD']``
* ``RIPPLE_TIMEOUT`` - timeout for django manamgement command calls
* ``RIPPLE_TRANSACTION_MONITOR_MIN_LEDGER_INDEX`` - offset, ledger index to start transaction monitoring with,
default is the beginning of time
Example Config::
RIPPLE_API_DATA = [
{
'RIPPLE_API_URL': 'http://s_west.ripple.com:51234',
'RIPPLE_API_USER': '',
'RIPPLE_API_PASSWORD': '',
}
] # You can specify multiple servers and ripple_api app will try them in order if one of servers
# returns error
Signals
=======
* ``ripple_api.signals.transaction_status_changed = Signal(providing_args=["old_status"])`` - sent
when existing Transaction's status is changed
* default django's post_save signal is useful to get new Transactions
.. TODO:
* docs on api usage
* docs on management command
Release files for django-ripple_api 0.0.49
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 | |
|---|---|---|---|---|
| django-ripple_api-0.0.49.tar.gz | 22.9 kB | Without provenance | Details |
Release files / django-ripple_api-0.0.49.tar.gz
| Download URL | django-ripple_api-0.0.49.tar.gz |
|---|---|
| Size | 22.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
40a622590292e6fdd02cd6aef20e0d002b365d096894b612d9ca3365919d8b0a
|
|
BLAKE2b-256 checksum How to use checksums |
38e4ccbe18163eabac634eb0973cfea04db39c45bb94d9ed5da1fd18fb10fe24
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/2.7
|
Security for django-ripple_api 0.0.49
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.
