mirror of https://github.com/Akkudoktor-EOS/EOS.git synced 2026-10-10 00:16:39 +00:00

Files

T

r0b2g1t f882f62164 fix: runtime config update ignored by config file

Runtime settings were handed back to pydantic-settings as init settings,
which rank below the config file and the environment. Any key already
present in EOS.config.json or in the environment silently discarded the
update, so a bulk PUT /v1/config returned 200 without applying anything,
while the granular PUT /v1/config/{path} endpoint kept working.

Add a dedicated runtime settings source ranked directly below the command
line arguments and record granular updates there as well, so both
endpoints share one store that survives re-evaluation of the settings
sources. Environment variables keep precedence over the config file for
all keys that were not set at runtime.

Also repairs revert_settings() and update(), which passed their data
through the same init settings.

Closes #1303

2026-09-13 13:42:21 +02:00

4.4 KiB

Raw Blame History

% SPDX-License-Identifier: Apache-2.0 (configuration-page)=

Configuration Guide

The configuration controls all aspects of EOS: optimization, prediction, measurement, and energy management.

Storing Configuration

EOS stores configuration data in a nested structure.

Some configuration keys are read-only and cannot be altered. These keys are either set up by other means, such as environment variables, or determined from other information.

Several endpoints of the EOS REST server allow for the management and retrieval of configuration data.

:::{admonition} Note :class: note Configuration changes inside EOS are updated in memory, meaning all changes will be lost upon restarting the EOS REST server unless the configuration is saved to the EOS configuration file. This can be done manually or is done automatically by default. :::

Save Configuration File

Configure EOS for AUTOMATIC (vs. MANUAL) configuration file update in case of configuration changes.

Use endpoint PUT /v1/config/file to save the current configuration to the EOS configuration file.

Load Configuration File

Use endpoint POST /v1/config/reset to reset the configuration to the values in the EOS configuration file.

Configuration Sources and Priorities

The configuration sources and their priorities are as follows:

Command Line Arguments: Provided at startup of the REST server
Settings: Provided during runtime by the REST interface
Environment Variables: Defined at startup of the REST server and during runtime
EOS Configuration File: Read at startup of the REST server and on request
Default Values

Runtime settings are kept until they are reset by POST /v1/config/reset. All other sources are re-evaluated on every configuration change, which keeps environment variable changes effective for all configuration keys that were not set during runtime.

Runtime Config Updates

The EOS configuration can be updated at runtime.

Use the following endpoints to change the current runtime configuration:

PUT /v1/config: Update the entire or parts of the configuration.

:::{admonition} Note :class: note Those updates are not persistent automatically. However it is possible to save the configuration to the EOS configuration file. See Save Configuration File above. :::

Environment Variables

All configuration keys can be set by environment variables prefixed with EOS_ and separated by __ for nested structures. Environment variables are case insensitive.

EOS recognizes the following special environment variables (case sensitive):

EOS_CONFIG_DIR: The directory to search for an EOS configuration file.
EOS_DIR: The directory used by EOS for data, which will also be searched for an EOS configuration file.

EOS Configuration File

The EOS configuration file provides persistent storage for configuration data. It can be modified directly or through the REST interface.

If you do not have a configuration file, it will be automatically created on the first startup of the REST server in a system-dependent location.

To determine the location of the configuration file used by EOS, ask the REST server. The endpoint GET /v1/config provides the general.config_file_path configuration key.

EOS searches for the configuration file in the following order:

The directory specified by the EOS_CONFIG_DIR environment variable
The directory specified by the EOS_DIR environment variable
A platform-specific default directory for EOS
The current working directory

The first configuration file available in these directories is loaded. If no configuration file is found, a default configuration file is created, and the default settings are written to it. The location of the created configuration file follows the same order in which EOS searches for configuration files, and it depends on whether the relevant environment variables are set.

Use the following endpoints to interact with the configuration file:

PUT /v1/config/file: Save the current configuration to the configuration file.
PUT /v1/config/reset: Reload the configuration file, all unsaved runtime configuration is reset.

Default Values

Some of the configuration keys have default values by definition. For most of the configuration keys the default value is just None, which means no default value.

:heading-offset: 1
:relative-docs: ..
:relative-images:

4.4 KiB Raw Blame History