Files
homelabstack/plans/homelab-improvements/tasks/TB-007-romhacks-handoff.md
T
ginnoirandClaude Sonnet 4.6 1bc648f33b fix(maintainerr): correct data volume path and enable TLS bypass for Plex
- Mount /config/maintainerr to /opt/data (actual DB location, not /opt/maintainerr/data)
- Add NODE_TLS_REJECT_UNAUTHORIZED=0 so Node.js accepts Plex's self-signed cert
- Mark TB-007/008/009/012/013/016 tasks as done/dropped in improvement plan

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-15 20:52:06 -05:00

1.6 KiB

TB-007 — Romhacks → RomM handoff

Status: done
Your call: Do it


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 Already working — 200+ games routed; handoff runs every 6h automatically
Notes 3 games still downloading (Vanguard, Vanishing Point, Eternal X/Wilting Y) — auto-placed next cycle. 5 re-appeared incoming folders are harmless JD re-download remnants.
Date 2026-06-15

Reference (only open if we're doing it)

Stack / files

stacks/romhacks/orchestrator/

If we do it — rough steps

  1. Complete handoff.py — incoming → Emulation/roms/
  2. RomM custom cover API
  3. Test with one staged folder

Done when

  • Test ROM in RomM after handoff
  • DRY_RUN still safe