Improve configuration robustness and fix Docker deployment#17
Merged
Conversation
Embed the defaults already defined in settings.yaml directly into the code. This ensures the application runs even if the configuration file is missing or incomplete, while keeping consistency with the documented defaults.
Contributor
Author
|
Validation of configuration values before use could further improve robustness, enabling either:
|
Member
|
Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes a configuration key mismatch in the Docker setup, makes the Valkey database number configurable, and embeds the documented defaults directly into the code. These changes ensure the application runs reliably even when configuration files are missing or incomplete.
Fixes #16