-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Add Hot-Reloading Feature for Config Files in OpenIM-Server with Viper #1506
Comments
This issue is available for anyone to work on. Make sure to reference this issue in your pull request. ✨ Thank you for your contribution! ✨ |
/accept |
Thank you for accepting this PR. I will closely follow your repository at https://github.com/charles-chenzz/open-im-server. It would be even more friendly if interested individuals could provide their input. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
please remove my repo link. Thanks |
/accept |
@Lansongxx This one does not support contributor participation for the time being, this one has been claimed by a contributor @charles-chenzz Check out the issue below if you're interested Or you can see that there are other features to try. Or you can create your own issue ~ thx |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
Checklist
Is this feature request related to a problem?
None
Problem Description
The OpenIM server currently utilizes Viper for configuration file parsing. While this is effective for initial loading, it lacks the ability to dynamically reload configurations at runtime.
Solution Description
Implement hot-reloading functionality in OpenIM server. This will allow the server to update configurations in real-time without needing a restart, whenever changes are made to the config files.
Benefits
Potential Drawbacks
no
Additional Information
Potential challenges in implementing hot-reloading with Viper.
Implications for current server performance and stability.
Best practices for managing and deploying configuration changes in a live environment.
The text was updated successfully, but these errors were encountered: