Omni (x)Extensions
Simple web application consuming the Omni API.
This application may be used as a supervisor of the Omni Platform to run tasks in an async fashion, this way it's possible to remove async tasks from the Omni core.
Usage
One must define a series of configuration values in order to correctly use the automated part of the omni extension (supervisor).
| Name | Type | Default | Description |
|---|---|---|---|
| OMNIX_REMOTE | bool |
False |
If the remote URL should be used as the default one (legacy). |
| OMNIX_USERNAME | str |
None |
The username to be used for authentication on the omni service. |
| OMNIX_PASSWORD | str |
None |
The password value used in the authentication on the omni service, notice that this value will be sent in plain text (using an SSL encrypted connection). |
| OMNIX_CLIENT_ID | str |
None |
The identifier of the Omni API client to be used for authentication. |
| OMNIX_CLIENT_SECRET | str |
None |
The secret string to be used by the Omni API client for authentication. |
| OMNIX_QUEUE | str |
omnix |
The name of AMQP queue that is going to be used. |
| OMNIX_RECORD_CHUNK | int |
300 |
The size of record chunk to be used by the scheduler (use carefully to avoid memory issues). |
| OMNIX_BIRTHDAY_TEMPLATE | str |
None |
If set allows for a remote definition of the base template to be used for email sending. |
| REMOTE | bool |
False |
If the remove mode should be used (production URL creation). |
| OMNIX_REMOTE | bool |
False |
Same as REMOTE. |
| OMNIX_SCHEDULE | bool |
True |
If the scheduling (background) operations of the Omnix should be enabled (defaults to True). |
| REDIRECT_URL | str |
None |
The URL that will be used for OAuth2 based callbacks. |
Additionally one must also configure the MongoDB and RabbitMQ instances to be able to execute
the proper master and slave supervisors. For that use the MONGOHQ_URL and CLOUDAMQP_URL variables.
FAQs
How can I flush the Slack sales message?
Use the following URL:
GET https://omnix.hive.pt/flush_slack_sales?offset=1
How can I flush the Slack previous (day) message?
Use the following URL:
GET https://omnix.hive.pt/flush_slack_previous?offset=1
License
Omnix is currently licensed under the Apache License, Version 2.0.
Build Automation
1 maintainer
Metadata
1 maintainer
Release files for omnix 0.3.17
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 |
|---|---|---|---|---|
| omnix-0.3.17.tar.gz | 56.8 kB | Without provenance | Details for omnix-0.3.17.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| omnix-0.3.17-py2-none-any.whl | Python 2 | none | any | Details for omnix-0.3.17-py2-none-any.whl |
Total release size: 159.2 kB
Release files / omnix-0.3.17.tar.gz
| Download URL | omnix-0.3.17.tar.gz |
|---|---|
| Size | 56.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bfb1d12f31b05780b6a29345d76f2d7ca1f5969d96086ffe5b6b719cb68b1e29
|
|
BLAKE2b-256 checksum How to use checksums |
25944c67fcee70db9c85d986e8d3b672e328701768596d76a0e33d4305b02061
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.8.3 requests/2.27.1 setuptools/44.1.0 requests-toolbelt/1.0.0 tqdm/4.64.1 CPython/2.7.18
|
Release files / omnix-0.3.17-py2-none-any.whl
| Download URL | omnix-0.3.17-py2-none-any.whl |
|---|---|
| Size | 102.5 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
56500d360c7f46cecef291df2c524c15661a0353682e283caba2c18a23667788
|
|
BLAKE2b-256 checksum How to use checksums |
43832da783421739783520618818d27b86f5e628b7ba0d9965f954497fea2972
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.8.3 requests/2.27.1 setuptools/44.1.0 requests-toolbelt/1.0.0 tqdm/4.64.1 CPython/2.7.18
|
Security for omnix 0.3.17
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.
