Snabbstart

English | 中文 | 日本語 | 한국어 | Français | Deutsch | Español | Português | Svenska | Suomi | Nederlands

Lagg till craten och de schema/runtime-bibliotek som programmet anvander:

[dependencies]
rust-config-tree = "0.1"
confique = { version = "0.4", features = ["yaml", "toml", "json5"] }
figment = { version = "0.10", features = ["yaml", "toml", "json", "env"] }
schemars = { version = "1", features = ["derive"] }
serde = { version = "1", features = ["derive"] }
clap = { version = "4", features = ["derive"] }

Definiera ett confique-schema och implementera ConfigSchema for rottypen:

#![allow(unused)]
fn main() {
use std::path::PathBuf;

use confique::Config;
use rust_config_tree::ConfigSchema;

#[derive(Debug, Config)]
struct AppConfig {
    #[config(default = [])]
    include: Vec<PathBuf>,

    #[config(nested)]
    server: ServerConfig,
}

#[derive(Debug, Config)]
struct ServerConfig {
    #[config(default = "127.0.0.1")]
    #[config(env = "APP_SERVER_BIND")]
    bind: String,

    #[config(default = 8080)]
    #[config(env = "APP_SERVER_PORT")]
    port: u16,
}

impl ConfigSchema for AppConfig {
    fn include_paths(layer: &<Self as Config>::Layer) -> Vec<PathBuf> {
        layer.include.clone().unwrap_or_default()
    }
}
}

Ladda konfigurationen:

#![allow(unused)]
fn main() {
use rust_config_tree::load_config;

let config = load_config::<AppConfig>("config.yaml")?;
println!("{config:#?}");
Ok::<(), Box<dyn std::error::Error + Send + Sync>>(())
}

Anvand en rotfil med rekursiva includes:

# config.yaml
include:
  - config/server.yaml

# config/server.yaml
server:
  bind: 0.0.0.0
  port: 3000

Standardprioriteten for load_config ar:

environment variables
  > config files, with later merged files overriding earlier files
    > confique code defaults

Nar includes laddas av hog-niva-API:t har rotfilen hogsta filprioritet. Inkluderade filer ger lagre prioriterade varden och kan anvandas for standardvarden eller sektionsspecifika filer.

Kommandoradsargument ar programspecifika, sa load_config laser dem inte automatiskt. Slå samman CLI-overrides efter build_config_figment nar programmet har override-flaggor for konfiguration:

CLI-flaggornas namn valjs av programmet. De ar inte automatiskt a.b.c-konfigurationssokvagar. Foredra normala clap-flaggor som --server-port, och mappa dem sedan till en nastlad override-struktur. Den nastlade serialiserade formen styr vilken konfigurationsnyckel som skrivs over.

Endast varden som representeras i programmets CliOverrides-provider skriver over konfiguration. Detta ar anvandbart for parametrar som ofta andras for en enskild korning utan att redigera konfigurationsfilen. Stabila varden bor ligga i konfigurationsfiler.

#![allow(unused)]
fn main() {
use figment::providers::Serialized;
use serde::Serialize;
use rust_config_tree::{build_config_figment, load_config_from_figment};

#[derive(Debug, Serialize)]
struct CliOverrides {
    #[serde(skip_serializing_if = "Option::is_none")]
    server: Option<CliServerOverrides>,
}

#[derive(Debug, Serialize)]
struct CliServerOverrides {
    #[serde(skip_serializing_if = "Option::is_none")]
    port: Option<u16>,
}

let cli_overrides = CliOverrides {
    server: Some(CliServerOverrides { port: Some(9000) }),
};

let figment = build_config_figment::<AppConfig>("config.yaml")?
    .merge(Serialized::defaults(cli_overrides));

let config = load_config_from_figment::<AppConfig>(&figment)?;
let _ = config;
Ok::<(), Box<dyn std::error::Error + Send + Sync>>(())
}

Med CLI-overrides sammanslagna pa detta satt ar full prioritet:

command-line overrides
  > environment variables
    > config files
      > confique code defaults