sneak/vaultik
1
0 Fork 0
Code Issues 6 Pull Requests 5 Actions 3 Packages Projects Releases Wiki Activity

Rewrite README.md and the other prose documents sentence by sentence (closes #397, closes #398) #399

Open
clawbot wants to merge 14 commits from docs/397-rewrite-prose-documents into next
pull from: docs/397-rewrite-prose-documents
merge into: sneak:next
Conversation 6 Commits 14 Files Changed 14
+12 -6
2 changed files with 12 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 1aea50d254 - Show all commits

No files matched your search

ARCHITECTURE.md
+6 -1
View File
@@ -257,7 +257,12 @@ data again.
itself:
- It copies the index into a temporary directory with `VACUUM INTO`.
- It deletes from the copy everything that does not belong to this snapshot.
- It deletes the rows of every other snapshot from the copy. It also deletes the
files and blobs that this snapshot does not use. It then deletes each chunk
that no remaining file and no remaining blob uses.
- It keeps the `local_meta` and `schema_migrations` tables as they are. The
uploaded database therefore names the destination, and lists the migrations
that have run.
- It runs `VACUUM`, so that no deleted row is left in the file.
- It compresses the copy with zstd and encrypts it with age.
- It builds the manifest from the copy.
docs/REPOSTRUCTURE.md
+6 -5
View File
@@ -60,8 +60,8 @@ not present:
The check is skipped when the look-up fails for any other reason. S3 refuses
the look-up to credentials that can only write. A machine with such credentials
therefore does not notice an emptied destination. Its next backup would leave
out the data its local index records as stored. After a destination is emptied,
therefore does not notice an emptied destination. Its next backup would not
upload data that its local index says is stored. After a destination is emptied,
run `vaultik database delete` on such a machine before it backs up again.
`remote nuke` deletes the marker last.
@@ -275,9 +275,10 @@ Back up a directory that outsiders can write to as a snapshot of its own.
### Chunk boundaries use no secret
The FastCDC parameters are fixed and public. With the default `chunk_size` of
10 MB, a chunk is between 2.5 MB and 40 MB. A file of 2.5 MB or less is one
chunk.
The FastCDC parameters are fixed and public. `chunk_size` sets the average chunk
size. No chunk is larger than four times this size. Only a file's last chunk can
be smaller than a quarter of it. With the default of 10 MB, those limits are 40
MB and 2.5 MB. A file of 2.5 MB or less is one chunk.
At the default `blob_size_limit` of 10 GB, a blob holds hundreds of chunks. The
size of the blob then does not show the size of any one chunk. A limit close to