Update BorgBase repo ID after recreation #144

Merged
eblume merged 1 commit from fix/borgbase-repo-id into main 2026-02-10 13:19:16 -08:00
Owner

Summary

  • Previous BorgBase repo (k04ljcd7) had corrupted segments from interrupted backup attempts
  • Recreated as u3ugi1x1 (same US region, same SSH key, same append-only settings)
  • Updates repo path in Ansible defaults and known_hosts hostname in tasks

Post-merge

  1. mise run provision-indri -- --tags borgmatic
  2. ssh indri 'mise x -- borgmatic init --encryption repokey --repository borgbase-offsite'
  3. mise x -- borgmatic create --repository borgbase-offsite --verbosity 1 --progress
## Summary - Previous BorgBase repo (k04ljcd7) had corrupted segments from interrupted backup attempts - Recreated as u3ugi1x1 (same US region, same SSH key, same append-only settings) - Updates repo path in Ansible defaults and known_hosts hostname in tasks ## Post-merge 1. `mise run provision-indri -- --tags borgmatic` 2. `ssh indri 'mise x -- borgmatic init --encryption repokey --repository borgbase-offsite'` 3. `mise x -- borgmatic create --repository borgbase-offsite --verbosity 1 --progress`
Previous repo had corrupted segments from interrupted backup attempts.
Recreated as u3ugi1x1 (same region, same SSH key, same settings).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
eblume merged commit f65d11d55b into main 2026-02-10 13:19:16 -08:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
eblume/blumeops!144
No description provided.