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â
| Layer | Source | Description |
|---|---|---|
| Main Framework Static Config | config.yaml | Loaded at startup, unchanged during process lifetime; covers service, logging, database, authentication, and other core components |
| Main Framework Dynamic Config | sys_config data table | Can 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 Config | Plugin independent config files | Plugins 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.
Related Documentsâ
Framework Static Configuration
Detailed explanation of the main framework config.yaml static configuration, covering configuration items, default values, and usage instructions for server, logger, database, jwt, session, health, scheduler, workspace, i18n, cluster, upload, and plugin groups, helping developers quickly understand and customize main framework runtime behavior.
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.
Best Practices and Production Recommendations
Production deployment configuration checklist, security recommendations, and best practices covering static configuration, runtime parameter key items, configuration boundaries, and security requirements â helping ops teams ensure system stability, security, and observability in production environments.