Skip to main content
Version: 0.5.x(Latest)

Introduction

LinaPro uses a layered configuration system that divides configuration into three levels: main framework static configuration, main framework dynamic configuration, and plugin business configuration. This design ensures core framework stability while providing flexibility for runtime adjustments and plugin extensions.

Configuration Layers

LayerSourceDescription
Main Framework Static Configconfig.yamlLoaded at startup, unchanged during process lifetime; covers service, logging, database, authentication, and other core components
Main Framework Dynamic Configsys_config data tableCan be hot-updated at runtime, overriding static defaults; cached in-process with 1 hour TTL; cluster mode maintains consistency via Redis revision sync
Plugin Business ConfigPlugin independent config filesPlugins have independent configuration scopes, reading config through a priority mechanism, isolated from main framework config

Configuration File Locations

The main framework default configuration file is located at:

apps/lina-core/manifest/config/config.yaml

The repository also provides a fully bilingual-annotated configuration template, suitable as a per-field reference:

apps/lina-core/manifest/config/config.template.yaml

Plugin configuration files are located in their respective plugin directories. For priority and reading details, see Plugin Business Configuration.

📄️Framework Dynamic Configuration

Detailed explanation of main framework runtime hot-updatable parameters, covering the sys_config data table-driven system built-in parameters and business plugin custom parameter classification management, backend runtime parameters, public frontend display parameters, and TZ environment variable — explaining parameter caching mechanisms, cluster sync strategies, and typical use cases, helping ops engineers dynamically adjust system behavior without restarting processes.

📄️Plugin Business Configuration

Plugin business configuration isolation from main framework config, the exclusive override strategy for config read priority, management of the plugin.<plugin-id> section in host config.yaml, the generic sys_config runtime parameter storage mechanism (including plugin custom entries), differences in config reading between source plugins and dynamic plugins, and the whitelist validation flow for host public configuration — helping plugin developers understand configuration management best practices and security constraints.