Standardizing Log Path: Migrating chat Service Startup Logs to _output/logs #397
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 focuses on enhancing our log management system, particularly by adjusting the startup log path for the chat service. Previously, the startup logs for the chat service were located in the
logs/
directory. This setup caused inconsistencies in path management and inconveniences in maintenance. To address this issue, we have decided to migrate the chat startup log path to_output/logs
.This change aligns the chat service's log path with that of our openim-server, unifying our project's log management approach. It also makes log storage and access more intuitive and efficient. This update is aimed at simplifying our log maintenance efforts and providing a more convenient path for future log analysis.
Link: #398
Key changes include:
logs/
to_output/logs
.