feat(logging): add file output option for logging configuration #1167
Conversation
This file contains 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.
The commit introduces the ability to log to a file in the logging system. In internal/app/log.go, new code has been added to handle logging to a specified file path. If no path is provided, it defaults to "go2rtc.log". Additionally, error handling ensures that problems during file opening or writing are logged appropriately.
This commit also updates the README.md to include documentation about a new logging output option (output: stdout), specifying that the available output options are stdout, stderr, or a file path. This provides clarity on the configurable logging output destinations directly from the README file.
Feature request from #1165