You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem with Real-time Webhook Integrated Autoupdate:
This implementation would rely solely on real-time webhooks, which may miss updates if mufbot is offline. If a release occurs during downtime, the webhook notification is lost, and the application will not receive it when restarted.
Proposed Solution
Implement a hybrid autoupdate mechanism combining:
Initial Startup Version Check
Real-time Webhook Notifications
Key Benefits
Ensures updates are not missed during application downtime
Provides seamless integration with real-time webhooks
Guarantees the application stays up-to-date upon restart
Enhances overall update reliability and accuracy
Minimizes potential errors and conflicts
Implementation Details
Initial Version Check on Startup:
Upon startup, the application will check the current version against the latest available version from github releases.
Real-time Webhook Connection:
Establish a real-time connection to receive webhook notifications for updates as they occur.
Important
Store Update History:
Maintain a log of update history for reference, allowing the application to track what updates were missed during downtime.
Handle Edge Cases:
Implement logic to manage scenarios where multiple updates occur during downtime, ensuring the application can apply all relevant updates in the correct order.
By adopting this hybrid approach, we can ensure our application stays current and functional, even when offline.
No description provided.
The text was updated successfully, but these errors were encountered: