Add Kopia backup stack with Backblaze B2 offsite target.

Protects /config, selective labdata, and nightly DB dumps; documents homelab improvement plan briefs.
This commit is contained in:
ginnoir
2026-06-10 21:21:34 -05:00
parent 225078afbe
commit 7c7f6dfebc
47 changed files with 3105 additions and 1 deletions
@@ -0,0 +1,60 @@
# TB-007 — Romhacks → RomM handoff
**Status:** not started
**Your call:** _(unset — talk first)_
---
## Talk first
> **Stop.** Don't read Reference until we've talked.
> In chat, say **"let's do TB-007"** or **"romhacks → romm handoff"**.
**In one sentence:** Finish the pipeline so downloaded ROM hacks land in RomM with cover art.
**Why it came up:** Orchestrator + JDownloader exist; moving files into the library isn't built yet.
### Questions
1. Is the Discord/JDownloader pipeline armed, or still theoretical?
2. Worth finishing before arming, or drop the whole romhacks stack?
3. How much automation vs 'I'll move files manually'?
### Your options
| Option | Meaning |
|--------|---------|
| **Do it** | We're doing this — I'll implement or walk you through it |
| **Later** | Keep on the list, not now |
| **Drop** | Remove from plan — totally fine |
| **Tweak** | Change scope; tell me how |
### What we decided
| | |
|---|---|
| **Decision** | |
| **Notes** | |
| **Date** | |
---
<details>
<summary>Reference (only open if we're doing it)</summary>
### Stack / files
stacks/romhacks/orchestrator/
### If we do it — rough steps
1. Complete handoff.py — incoming → Emulation/roms/<platform>
2. RomM custom cover API
3. Test with one staged folder
### Done when
- [ ] Test ROM in RomM after handoff
- [ ] DRY_RUN still safe
</details>