713ed830a3
Same MinIO, its own bucket, as asked. The audio-backups bucket is created; what remains is a MinIO IAM change, which needs root credentials — my permission layer blocked that call, so it is a script to run rather than something I applied. The script is additive and reversible: it attaches a second policy covering only the new bucket and carries the existing generated-images grant over rather than replacing it (attaching only the new one would break image storage). It prints the AUDIO_BACKUPS_S3_* values to set, and how to undo. A bucket policy alone does not work here: MinIO evaluates the user policy first and it denies by default. Verified — the app key gets AccessDenied on the new bucket until its own policy allows it. TODO records that, and the indexer being repointed from Documents to Personal assistant so mail is finally reached. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Dv6sqaY6Vq3ChZHMem3cnU |
||
|---|---|---|
| .. | ||
| build-image.sh | ||
| e2e.sh | ||
| enable-audio-backup-bucket.js | ||
| import-milestones.js | ||
| lint-references.js | ||
| maintenance.js | ||
| release.sh | ||
| test-generated-images.sh | ||