mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-17 15:42:24 +00:00
Merge the precise off-host deletion note
This commit is contained in:
commit
25ba09e714
5 files changed
+32
-18
No files matched your search
@@ -41,7 +41,7 @@ the restore script needs no flag to tell them apart.
|
||||
| `BACKUP_S3_ACCESS_KEY` | yes | |
|
||||
| `BACKUP_S3_SECRET_KEY` | yes | |
|
||||
| `BACKUP_S3_REGION` | no | defaults to `auto` (Cloudflare R2) |
|
||||
| `BACKUP_RETENTION_DAYS` | no | defaults to `30` |
|
||||
| `BACKUP_RETENTION_DAYS` | no | not read by the app; the number for your bucket's lifecycle rule |
|
||||
|
||||
## Bucket permissions
|
||||
|
||||
@@ -56,8 +56,9 @@ Cloudflare R2 the **Object Read & Write** token already covers all three.
|
||||
|
||||
The worker never deletes a backup object: its grant covers PutObject,
|
||||
GetObject and AbortMultipartUpload only, so a compromised worker cannot
|
||||
wipe the history. Expiry is the storage provider's lifecycle rule, set to
|
||||
match `BACKUP_RETENTION_DAYS`:
|
||||
wipe the history, and nothing in the app reads `BACKUP_RETENTION_DAYS`.
|
||||
Expiry is the storage provider's lifecycle rule, set to match the number
|
||||
you wrote there:
|
||||
|
||||
```
|
||||
Filter: "" (all objects)
|
||||
|
||||
Reference in new issue
Block a user