How to modify AppContext or build global methods?

[ISensuiI]

How to modify AppContext or build global methods?

I just started using loco. I read the website and docs help documents in detail. I learned that AppContext can carry most global component objects, but I actually need to register some custom components, such as redis...
Since I just started using axum and loco recently, my understanding may not be correct. I read redis.rs in detail and did not find that it supports axum middle layer, etc. Then the way I thought of was to parse the connection information from the configuration normally, then initialize and obtain the redis client and put it in a static global variable. But I didn't find that loco has relevant configuration options. To save these custom objects.
Do I need to manage global variables myself in this case? I read the relevant code and manual of AppContext, and AppContext does not seem to support inserting objects by itself.

[kaplanelad]

Currently, the AppContext cannot be modified directly.

Could you share what you're trying to achieve? I'd be happy to help you find the best way to implement it.

[ISensuiI]

#[allow(clippy::module_name_repetitions)]
pub struct RedisInitializer;

// 定义与配置文件对应的结构体
#[derive(Serialize, Deserialize, Default, Debug, Clone)]
pub struct RedisSettings {
pub uri: String,
pub max_connections: usize,
}

#[derive(Serialize, Deserialize, Default, Debug, Clone)]
pub struct Settings {
pub redis: Option,
}

impl Settings {
pub fn from_json(value: &serde_json::Value) -> Result {
Ok(serde_json::from_value(value.clone())?)
}
}

#[async_trait]
impl Initializer for RedisInitializer {

fn name(&self) -> String {
    "redis-cache".to_string()
}

async fn after_routes(&self, router: Router, ctx: &AppContext) -> Result<Router, loco_rs::Error> {
    
    // 从配置中提取Redis设置
    let redis_settings = if let Some(settings_json) = &ctx.config.settings {
        let settings = Settings::from_json(settings_json)
            .map_err(|e| loco_rs::Error::Any(e.into()))?;
        settings.redis.ok_or_else(|| {
            loco_rs::Error::Any(anyhow::anyhow!("Redis配置未找到").into())
        })?
    } else {
        return Err(loco_rs::Error::Any(anyhow::anyhow!("未找到settings配置").into()));
    };
    
    // 创建Redis服务
    let redis_service = RedisManager::new(redis_settings.uri.clone()).await.map_err(|e| loco_rs::Error::Any(Box::from(e)))?;
    
    GlobalState::init_server_manager(redis_service).await.map_err(|e| loco_rs::Error::Any(e.into()))?;
    
    info!("Redis服务已成功初始化，连接到: {:?}", redis_settings.uri);

    Ok(router)
}

}

---

#[derive(Educe)]
#[educe(Debug)]
pub struct RedisManager {
#[educe(Debug(ignore))]
pool: Arc<Pool>,
}

impl RedisManager {

pub async fn new(redis_uri:String) -> Result<Self> {
    
    info!(target:"app::common::database::config", "Redis 准备初始化");
    
    // let client = Client::open(redis_uri).map_err(|e| {
    //     error!(target: "app::common::database::config", "Redis 准备初始化失败: {}", e);
    //     anyhow::anyhow!("Redis 准备初始化失败: {}", e)
    // })?;

    // 创建 RedisConnectionManager
    let manager = RedisConnectionManager::new(redis_uri).map_err(|e| {
        error!(target: "app::common::database::config", "Redis 连接管理器创建失败: {}", e);
        anyhow::anyhow!("Redis 连接管理器创建失败: {}", e)
    })?;

    let pool = Pool::builder()
        .max_size(15) // 设置最大连接数
        .build(manager)
        .await
        .map_err(|e| anyhow::anyhow!("Redis 连接池创建失败: {}", e))?;

    info!(target: "app::common::database::config", "Redis 初始化成功");
    Ok(Self { pool: Arc::new(pool) })
}

// 获取连接池中的连接
pub async fn get_conn(&self) -> Result<PooledConnection<'_, RedisConnectionManager>> {
    self.pool.get().await.map_err(|e| anyhow::anyhow!("获取Redis连接失败: {}", e))
}

---

pub static GLOBAL_STATE: LazyLock = LazyLock::new(|| GlobalState::new());

#[derive(Debug)]
pub struct GlobalState {
pub(crate) global_redis_manager: OnceLock<Arc>,
}

Thank you for your reply. I will paste my code for you to analyze. I am not familiar with loco at the beginning. For example, I need to introduce a redis. I understand that redis can be introduced through the middle layer. But my module is not an independent processing module that does not want to go through the middle layer. So I use the init part below for initialization. After initialization, I cannot modify the AppContext. So I can only initialize the module with global static variables and then call it where needed. In this case, does the loco framework provide relevant global storage or global state storage?

[ISensuiI]

https://loco.rs/docs/the-app/controller/
I mentioned some issues about state preservation before. Since the loco manual is quite complicated, I missed some parts when I first read it, which led me to build state preservation myself. In fact, the page above clearly shows how to save custom state information.