-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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: Global maintenance endpoint #3837
Comments
Data migrations are complex and at the moment we do not have an ability to control how the instance behave during version update. We do consider to put more effort into this a part of a future enterprise version for orgs that need zero-downtime upgrades. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🔖 Feature description
A global maintenance endpoint that can be enabled globally for every project and gets automatically enabled if Appwrite gets upgraded. Maybe this must be a different micro service, running completely individually on another port.
🎤 Pitch
While I was upgrading to the newest Appwrite version, I noticed how long it takes to migrate my data. While the migration script was running, the most projects didn't work.
It would be awesome to check on the frontend if the Appwrite instance is in maintenance mode. So you could return a maintenance screen instead of a application that doesn't work because Appwrite is upgrading.
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: