Implement backups, commit and restoration
This commit is contained in:
@@ -7,12 +7,11 @@ unknown fields, malformed labels, invalid Base64, and oversized bundles.
|
||||
|
||||
## Version 1 structure
|
||||
|
||||
For M4, the current encrypted bundle is intended to live at
|
||||
The current encrypted bundle lives at
|
||||
`ResolvedSettings::data_directory.join("vault.toml")`. This stable filename is
|
||||
relative to the resolved data directory, whose default is `Backup/data` beside
|
||||
the executable. M3 only prepares and serializes vault bytes in memory; it does
|
||||
not create this file or install application state. M4 persistence will own that
|
||||
write.
|
||||
the executable. The application installs the opaque serialized bytes through
|
||||
the saved-file transaction after completing its mandatory pre-Commit backup.
|
||||
|
||||
The top level contains:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user