glimr_redis/redis

Redis Entry Point

Application boot needs to wire up cache pools and session stores, but the underlying config parsing and pool construction are spread across several internal modules. This module is the public entry point that ties them together — each function takes a name or pool and returns a ready-to-use resource, so the app’s main module reads as a simple sequence of start calls rather than manual config loading and plumbing.

Values

pub fn session_store(name: String) -> store.SessionStore

Sessions need a backing store, and Redis is the go-to for multi-server deployments where in-memory stores won’t work. This starts a Redis pool and returns a SessionStore you can pass straight to session.setup() in your bootstrap — same one-liner pattern as starting a cache.

pub fn start(name: String) -> cache.CachePool

Without this, every app’s main module would need to import the config loader, the driver module, and the pool module just to get a cache going — three imports and four lines of boilerplate repeated in every project. This collapses all of that into a single call with just a name.

Search Document