Integrate runtime settings across setup, webserver, and bot - #14
Closed
Dadud wants to merge 4 commits into
Closed
Conversation
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
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.
Summary
This PR makes the setup/settings console control real runtime behavior across the webserver and bot:
.envbefore defaults for runtime config.envbot.jsAI summary/Ask AI, public audio URLs, transcription providers, and storage paths to use runtime settingsVerification
npm testnpm run check:syntaxnpm run check:configNotes
This keeps the existing map UI intact and focuses on making setup/settings additive and operational. Some settings are still marked restart-required where hot-swapping could be risky for long-running processes.