Index
Install
pip install pyfirebird
Firebird Console
It provides a Web UI for pipeline management.
Configurations
~/.firebird/config
This file contains configuration for mysql, rabbitmq and zookeeper. Here is an example:
{
"zookeeper": {
"hosts": "zookeeper:2181"
},
"rabbitmq": {
"username": "stonezhong",
"password": "changeme",
"host": "rabbitmq",
"port": 5672,
"heartbeat": 300
},
"mysql": {
"db_name": "firebird",
"username": "stonezhong",
"password": "changeme",
"server": "10.2.0.29"
}
}
~/.kube/config
This is your kubernete config file. Firebird Console need to talk to kubernete clsuter to start, stop pipelines.
~/.oci/config
This is needed if you are using Kubernete in Oracle Cloud Infrastructure. It is your oci config file. You may also need the key file referenced by this config file.
Environment Variables
CONSOLE_URI_BASE
firebird console will read this variable and assuming this is the base url for firebird console. It is commonly used if you put firebird console behind a reverse proxy under certain path.
# Example
export CONSOLE_URI_BASE=/streaming/console
CSRF_TRUSTED_ORIGINS
It firebird console uses SSL, you need to specify the domain so HTTP post request won't be rejected due to CRRF trust issue.
# Example
export CSRF_TRUSTED_ORIGINS=https://myserver.com
Initialize Firebird Console Database
fbconsole migrate
Start Firebird Console
fbconsole runserver <ip>:<port>
# Example:
fbconsole runserver 0.0.0.0:8000
# You can access firebird console at $CONSOLE_URI_BASE/ui/
Common commands
Register a Pipeline
pipeline register \
--pipeline-module-name <pipeline name> \
--pipeline-namespace-name <pipeline namespace name> \
--pipeline-image-name <pipeline image name>
# example
pipeline register \
--pipeline-module-name pipe \
--pipeline-namespace-name firebird \
--pipeline-image-name iad.ocir.io/idrnu3akjpv5/firebird-app1
Unregister a Pipeline
pipeline unregister -pid <pipeline name>
Start a Pipeline
pipeline start -pid <pipeline name>
Stop a Pipeline
pipeline stop -pid <pipeline name>
List Pipelines
pipeline list
Metadata
Release files for pyfirebird 0.0.115
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 |
|---|---|---|---|---|
| pyfirebird-0.0.115.tar.gz | 233.1 kB | Without provenance | Details for pyfirebird-0.0.115.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyfirebird-0.0.115-py3-none-any.whl | Python 3 | none | any | Details for pyfirebird-0.0.115-py3-none-any.whl |
Total release size: 473.3 kB
Release files / pyfirebird-0.0.115.tar.gz
| Download URL | pyfirebird-0.0.115.tar.gz |
|---|---|
| Size | 233.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9012461805d50a526f92d883fbdb251196295effdbfb8de4f33723c00ff928ab
|
|
BLAKE2b-256 checksum How to use checksums |
73eacb7a55c354d1882b215a9e27b445d5a933be68281236e69c54ea3222ce19
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Release files / pyfirebird-0.0.115-py3-none-any.whl
| Download URL | pyfirebird-0.0.115-py3-none-any.whl |
|---|---|
| Size | 240.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b8752ac8bda0eaacc3f3431914a2ff9b01d48af34270664e89e8f5277008f857
|
|
BLAKE2b-256 checksum How to use checksums |
8aa4719acd8c1f464225caad1ebcb8771d5e5311c90cc9f7d6cf628c9d4b9e62
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Security for pyfirebird 0.0.115
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.