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
{{ message }}
This repository has been archived by the owner on Jun 7, 2022. It is now read-only.
We need for as save upgrade into the next version do a complete backup.
My idea is create in the master a folder named backup. In this folder we create another one with the timestamp and extra information. Inside this folder we have a complete backup of the cloud.
Thats allows us to upgrade/migrate some stuff from old version into new version. When something is wrong, we can do easy a complete rollback
The text was updated successfully, but these errors were encountered:
It is better when the upgrade works always correctly.
We could inform the users on the Discord Server, that they should do a backup before upgrading, but we can't just copy everything, this suddenly increases the disk space consumption immensely, which could cause the server to run out of disk space
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We need for as save upgrade into the next version do a complete backup.
My idea is create in the master a folder named
backup
. In this folder we create another one with the timestamp and extra information. Inside this folder we have a complete backup of the cloud.Thats allows us to upgrade/migrate some stuff from old version into new version. When something is wrong, we can do easy a complete rollback
The text was updated successfully, but these errors were encountered: