Skip to content

Allow user to overwrite settings - #13

Merged
fillipe-gsm merged 2 commits into
masterfrom
6-allow-user-to-overwrite-settings
Nov 8, 2025
Merged

Allow user to overwrite settings#13
fillipe-gsm merged 2 commits into
masterfrom
6-allow-user-to-overwrite-settings

Conversation

@fillipe-gsm

@fillipe-gsm fillipe-gsm commented Nov 8, 2025

Copy link
Copy Markdown
Owner

Handles #6

Description

It is now possible to overwrite the existing settings with either:

  • Creating environment variables prefixed by KB_, such as KB_DB_NAME; or
  • Creating a kb_settings.toml file with only the variables you want to overwrite. In this case, the KB_ prefix and usage of uppercase is not required.

Keep in mind that it is extremely advisable to not update these parameters for existing files.

The verification that there are inconsistencies is too cumbersome, and I decided to give freedom (and responsibility) to the user.

The previous variable `default_db_name` made no sense as there are no
other variables overwriting this.

And even if the user wishes to do so, he/she can do it via env variables
or another `.toml` file
The user can overwrite everything by creating a `kb_settings.toml` file
instead of just creating environment variables
@fillipe-gsm
fillipe-gsm merged commit 6597665 into master Nov 8, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant