Config

Application configuration is a common yet tricky problem, especially in real-world projects.

You often need to create dependencies that rely on dynamic settings — such as setting a database engine's isolation level, or adjusting timeouts based on environment.

Lihil provides a unified configuration system that supports multiple sources — files, environment variables, and CLI arguments — allowing secure and flexible config management out of the box.

---

Config Loading & Parsing

from lihil.config import lhl_read_config, AppConfig

Lihil automatically loads configuration values from the following sources, in order of increasing priority:

1. User-provided config files
2. Environment variables
3. Command-line arguments

This layered approach reflects real-world needs:

• Static and public config, such as server ports or logging levels, can go into a versioned file (e.g. settings.toml).

• Sensitive data, like API keys or database passwords, should come from environment variables to avoid accidental exposure.

• For temporary overrides, like debugging with a different port or toggling a flag, CLI arguments offer maximum flexibility.

Read config from different sources

config = lhl_read_config("settings.toml", config_type=MyAppConfig)

This automatically reads from all three sources and merges them into one config instance.

You can provide multiple files and they will be read in order.

config = lhl_read_config("settings.toml", "dev.env", "prod.env")

Set Config Manually

from lihil import AppConfig, Lihil

lhl = Lihil(app_config = AppConfig())

Or use lhl_set_config() directly:

from lihil.config import lhl_set_config

lhl_set_config(MyConfig())

Calling without arguments resets to the default:

lhl_set_config()

Get Current Config

Use lhl_get_config() to retrieve the active config from anywhere in your app:

from lihil.config import lhl_get_config

config = lhl_get_config()

Extending AppConfig

You can extend AppConfig to define your own settings:

from lihil.app_config import AppConfig

class MyAppConfig(AppConfig):
    my_custom_setting: str = "default"

Then load it:

from lihil.config import lhl_read_config

config = lhl_read_config("settings.toml", config_type=MyAppConfig)

Auto generated command line arguments

If you extend your config via inheriting from AppConfig, the extra properties will also be generated as command line arguments and you can pass them to override.

Example Config File (config.toml)

[lihil]
IS_PROD = true
VERSION = "1.0.0"

[lihil.server]
HOST = "127.0.0.1"
PORT = 9000

[lihil.oas]
TITLE = "My API"

Command-line Overrides

Any field can be overridden via CLI:

python app.py --is_prod --server.port 8080

Using Other Config Schemas (e.g., Pydantic)

If you use a different validation system like Pydantic, you can parse it yourself and inject it manually:

from lihil.config import lhl_set_config, lhl_get_config

app_config = PydanticSettings()
lhl_set_config(app_config)

Your config is expected to implement the IAppConfig interface.

AppConfig Interface

    class IOASConfig(Protocol):
        @property
        def OAS_PATH(self) -> str: ...
        @property
        def DOC_PATH(self) -> str: ...
        @property
        def TITLE(self) -> str: ...
        @property
        def PROBLEM_PATH(self) -> str: ...
        @property
        def PROBLEM_TITLE(self) -> str: ...
        @property
        def VERSION(self) -> str: ...

    class IServerConfig(Protocol):
        @property
        def HOST(self) -> str: ...
        @property
        def PORT(self) -> int: ...
        @property
        def WORKERS(self) -> int: ...
        @property
        def RELOAD(self) -> bool: ...
        @property
        def ROOT_PATH(self) -> bool: ...
        def asdict(self) -> dict[str, Any]: ...

    class IAppConfig(Protocol):
        @property
        def VERSION(self) -> str: ...
        @property
        def server(self) -> IServerConfig: ...
        @property
        def oas(self) -> IOASConfig: ...

Summary

• Inherit AppConfig to extend, use lhl_read_config to load config, then set config via lhl_set_config for most cases
• If you build the config manually (e.g. via Pydantic), imlement the IAppConfig interface.
• Call lhl_get_config to access the config anywhere.
• Sensitive values should go into environment variables.
• Use CLI arguments for fast, local overrides, for example, debugging.