tigrbl_engine_redis
Redis engine plugin for cache, data structures, and Tigrbl engine workflows backed by Redis.
What is tigrbl_engine_redis?
Redis engine plugin for cache, data structures, and Tigrbl engine workflows backed by Redis.
Why use tigrbl_engine_redis?
Use it when a Tigrbl application needs this backend without installing every engine package.
When should I install tigrbl_engine_redis?
Install it when the storage, analytics, cache, or integration workload named by this package is the intended runtime backend.
Who is tigrbl_engine_redis for?
Application developers, data platform engineers, and operators choosing concrete persistence or data-plane behavior.
Where does tigrbl_engine_redis fit?
tigrbl_engine_redis lives at pkgs/90_engines/tigrbl_engine_redis and serves Redis-backed cache and data-structure workflows.
How does tigrbl_engine_redis work?
It exposes a tigrbl.engine entry point and a package register() hook so Tigrbl can discover or load the backend at runtime.
Install
uv add tigrbl_engine_redis
pip install tigrbl_engine_redis
Surface Coverage
| Surface | Value |
|---|---|
| PyPI package | tigrbl_engine_redis |
| Repository path | pkgs/90_engines/tigrbl_engine_redis |
| Python import root | tigrbl_engine_redis |
| Console scripts | none declared |
| Entry points | tigrbl.engine |
| Optional extras | none declared |
| Legal files | LICENSE, NOTICE |
| Supported Python | `3.10 |
What It Owns
tigrbl_engine_redis owns the engine plugin boundary. It should be installed when you need this package's focused responsibility without assuming every other Tigrbl workspace package is present.
Implementation orientation:
tigrbl_engine_redis: engine, session
Public API and Import Surface
- Import roots:
tigrbl_engine_redis. - Public symbols:
RedisEngine,RedisSession,redis_engine,register. - Workspace dependencies:
tigrbl. - External runtime dependencies:
redis>=5.0.0.
Usage Examples
Verify the installed package
python -m pip show tigrbl_engine_redis
python - <<'PY'
from importlib.metadata import version
print(version("tigrbl_engine_redis"))
PY
Register the engine plugin explicitly
from tigrbl_engine_redis import register
register()
Discover the engine through package metadata
from importlib.metadata import entry_points
for entry_point in entry_points(group="tigrbl.engine"):
if entry_point.module.startswith("tigrbl_engine_redis"):
plugin_register = entry_point.load()
plugin_register()
Install alongside the facade
uv add tigrbl tigrbl_engine_redis
pip install tigrbl tigrbl_engine_redis
How To Choose This Package
Choose tigrbl_engine_redis when the quick-answer table matches your use case. Choose tigrbl instead when you want the full public facade. Choose a lower-level package such as tigrbl-core, tigrbl-base, or tigrbl-runtime when you are building framework extensions or testing a specific internal boundary.
Related Packages
tigrbltigrbl-coretigrbl-runtimetigrbl_engine_sqlitetigrbl_engine_postgrestigrbl_engine_duckdbtigrbl_engine_pandas
Documentation Links
- Workspace docs
- Package catalog
- Package layout
- Current target
- Current state
- SSOT registry
- Release workflow
Support
- Community: Discord.
- Issues: GitHub Issues.
- Repository: pkgs/90_engines/tigrbl_engine_redis.
Package-local Boundary
This README is the package-local distribution entry point for tigrbl_engine_redis. It answers install, usage, API, ownership, and certification-orientation questions for this package. Broader architectural decisions, release status, and cross-package proof chains remain in the repository-level docs and SSOT registry.
Certification Status
- Package status: governed package in the
tigrbl/tigrblworkspace. - Governance source: SSOT registry.
- Release evidence: publish workflow validates package builds, tests, GitHub release assets, and PyPI publication for managed packages.
- Local certification guard:
pkgs/97_tests/tigrbl_tests/tests/unit/test_package_badges_and_notices.pyverifies every package README keeps the Discord badge, Apache 2.0 badge, explicit Python-version badge,LICENSE, andNOTICE. - Scope note: this README documents the package boundary. Runtime feature support remains governed by
.ssot/entities and the conformance docs linked below.
License
Licensed under the Apache License, Version 2.0. See LICENSE, NOTICE, and the official Apache 2.0 license text.
Metadata
Release files for tigrbl_engine_redis 0.4.5
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 |
|---|---|---|---|---|
| tigrbl_engine_redis-0.4.5.tar.gz | 19.1 kB | Without provenance | Details for tigrbl_engine_redis-0.4.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tigrbl_engine_redis-0.4.5-py3-none-any.whl | Python 3 | none | any | Details for tigrbl_engine_redis-0.4.5-py3-none-any.whl |
Total release size: 35.2 kB
Release files / tigrbl_engine_redis-0.4.5.tar.gz
| Download URL | tigrbl_engine_redis-0.4.5.tar.gz |
|---|---|
| Size | 19.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e9040ea89aa3f172e09adfbac4c7805a369a92513a161deb35e5b1475c9304d0
|
|
BLAKE2b-256 checksum How to use checksums |
201b3416ce6ab54f2ae5a92102911eaf69970460bf54d407aba8d8c2dd24913a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / tigrbl_engine_redis-0.4.5-py3-none-any.whl
| Download URL | tigrbl_engine_redis-0.4.5-py3-none-any.whl |
|---|---|
| Size | 16.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aa6ce785e4ab5c61adc05b0235e043f3350469655a42babd3be35197cec294c1
|
|
BLAKE2b-256 checksum How to use checksums |
860f7aaf5523e4ca57f32f69f915647523fda01acceb844d2276e374c5f54ae3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for tigrbl_engine_redis 0.4.5
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.