feat: store encrypted backup in platform-native cloud #518
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
daniel-mader
force-pushed
the
feat/cloud-backup
branch
from
25b9f1f to
b9a5a40
Compare
daniel-mader
force-pushed
the
feat/cloud-backup
branch
from
b9a5a40 to
75e5b57
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of change
When enabled, all files and assets created by UniMe are compressed and encrypted with the user's password.
The archive is then uploaded to the platform-native cloud provider (iCloud, Google Drive).
When a new profile is created in UniMe, the user is presented with an option to restore an existing profile from a backup (if exists).
Links to any relevant issues
closes #61
depends on tauri-apps/tauri#12682
How the change has been tested
n/a
Definition of Done checklist
Add an
xto the boxes that are relevant to your changes.