Mirrors/EOS
1
0
Fork 0
mirror of https://github.com/Akkudoktor-EOS/EOS.git synced 2026-04-19 04:06:20 +00:00
Code Issues Actions 6 Packages Projects Releases Wiki Activity

fix: optimization fail after restart (#1007)
Some checks failed
Bump Version / Bump Version Workflow (push) Has been cancelled
Details
CodeQL Advanced / Analyze (actions) (push) Has been cancelled
Details
CodeQL Advanced / Analyze (python) (push) Has been cancelled
Details
docker-build / platform-excludes (push) Has been cancelled
Details
pre-commit / pre-commit (push) Has been cancelled
Details
Run Pytest on Pull Request / test (push) Has been cancelled
Details
docker-build / build (push) Has been cancelled
Details
docker-build / merge (push) Has been cancelled
Details
Close stale pull requests/issues / Find Stale issues and PRs (push) Has been cancelled
Details

Browse Source 
Fix documentation for the loadforecast_power_w key.

Fix documentation to explain the usage of import file/ JSON string to
primarily initialise prediction data.

Fix code scanning alert no. 6: URL redirection from remote source

Enable to automatically save the configuration to the configuration file
by default, which is a widespread user expectation.

Make the genetic parameters non optional for better pydantic compliance.

Update:
- bump pytest to 9.0.3
- bump pillow to 12.2.0
- bump platformdirs to 4.9.6
- bump typespyyaml to 6.0.12.20260408
- bump tzfpy to 1.2.0
- bump pydantic to 2.13.0
- bump types-requests to 2.33.0.20260408

Signed-off-by: Bobby Noelte <b0661n0e17e@gmail.com>
Co-authored-by: Normann <github@koldrack.com>
This commit is contained in:
Bobby Noelte
2026-04-15 08:48:56 +02:00
committed by GitHub
parent 29cc3d7f3b
commit 6f28022ed0
19 changed files with 717 additions and 671 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
docs/akkudoktoreos/configuration.md
View File

@@ -8,9 +8,7 @@ management.
## Storing Configuration
EOS stores configuration data in a `nested structure`. Note that configuration changes inside EOS
are updated in memory, meaning all changes will be lost upon restarting the EOS REST server if not
saved to the `EOS configuration file`.
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.
@@ -18,8 +16,18 @@ 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`.
@@ -39,13 +47,18 @@ The configuration sources and their priorities are as follows:
### Runtime Config Updates
The EOS configuration can be updated at runtime. Note that those updates are not persistent
automatically. However it is possible to save the configuration to the `EOS configuration file`.
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](#save-configuration-file) above.
:::
### Environment Variables
All `configuration keys` can be set by environment variables prefixed with `EOS_` and separated by