Sidecar SDK
stigg.api field which returns the same client as the Stigg.create_client SDK function. You can:
- Use
stigg.apiwherever you would otherwise useStigg.create_client - Rely on exactly the same interface and behavior
- Know that the Sidecar SDK depends on the same underlying API client and simply exposes it for convenience
Available options
Execution of the Sidecar service can be customized using the following environment variables:The server API key of the environment.
The URL of the Stigg API.
The Edge URL from which entitlements will be accessed.
Whether to listen for updates using WebSockets.
The WebSocket API URL.
Identifier of the environment, used to prefix the keys in Redis. If provided, Redis will be used as the cache layer.
Redis host.
Redis port.
Redis DB identifier.
Redis username.
Redis password.
Redis use TLS encryption. (Default=0)
Time period for Redis to keep the data before eviction in seconds.
Global entitlement fallback strategy in JSON format.
Service port (HTTP/2)
Deprecated TLS service port (HTTP/2 TLS)
Maximum size of the in-memory cache in bytes. If not set, the Sidecar allocates up to 50% of the available memory.
Health endpoint URL.
Ready endpoint URL.
Log level, can be one of:
error, warn, info, debug.Log string key for the ‘message’ in the JSON object.
Log string key for the ‘error’ in the JSON object.
Enables offline mode for local development.
Error handling
When the Sidecar encounters startup errors, such as an invalid API key or network errors to the Stigg API, it continues to run and serves entitlements from the:- Persistent cache (if available)
- Global fallback strategy
