Files
unraid-docker-manager/.planning/ROADMAP.md
T
Lucas Berger 6a0551e0d6 chore: archive v1.1 audit and add tech debt to Phase 11
Archived:
- milestones/v1.1/v1.1-MILESTONE-AUDIT.md
- milestones/v1.1/INTEGRATION-CHECK.md

Updated:
- ROADMAP.md: Added v1.1 tech debt to Phase 11
- STATE.md: Updated with tech debt tracking

Tech debt items added to Phase 11:
- README.md documentation (still shows direct socket)
- Duplicate --max-time flags in image pull
- Update flow duplication between single/batch paths

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-02-04 11:16:03 -05:00

94 lines
2.8 KiB
Markdown

# Roadmap — Unraid Docker Manager
## Milestones
- **v1.0 Docker Control via Telegram** — Phases 1-5 (shipped 2026-02-02) -> [Archive](milestones/v1.0-ROADMAP.md)
- **v1.1 n8n Integration & Polish** — Phases 6-9 (shipped 2026-02-04) -> [Archive](milestones/v1.1-ROADMAP.md)
- **v1.2 Modularization & Polish** — Phases 10-12 (planned)
---
## v1.2: Modularization & Polish
Complete remaining v1.1 scope: modularize workflow for maintainability, fix webhook issues, audit environment variables, and clear Unraid update badges.
### Phase 10: Workflow Modularization
**Goal:** Break main workflow into modular sub-workflows for maintainability
**Dependencies:** None
**Requirements:** TBD (carried from Phase 9.1)
**Plans:** 0 plans
Plans:
- [ ] TBD (run /gsd:plan-phase 10 to break down)
**Success Criteria:**
[To be defined during planning]
---
### Phase 11: Polish & Audit
**Goal:** Clear Unraid update badges, fix webhook issues, verify environment configuration, and address v1.1 tech debt
**Dependencies:** Phase 10 (modularization complete before polish)
**Requirements:** UNR-01, ENV-01, ENV-02, WEB-01
**Plans:** 0 plans
Plans:
- [ ] TBD (run /gsd:plan-phase 11 to break down)
**Success Criteria:**
1. After bot successfully updates a container, Unraid UI no longer shows "update available" for that container
2. Documentation clarifies whether TELEGRAM_USERID env var is required or can be hardcoded
3. Documentation clarifies whether TELEGRAM_BOT_TOKEN env var is required or if n8n credential suffices
4. Telegram webhook works when workflow is published (bot responds without manual execute)
**Tech Debt from v1.1 (to address):**
- README.md lines 14-34: Still documents direct docker.sock mounting (should document proxy architecture)
- Duplicate --max-time flags in image pull command (600 then 5, last wins — should keep only 600s)
- Update flow duplicated between single and batch paths (consolidation opportunity)
---
### Phase 12: Documentation Overhaul
**Goal:** [To be planned]
**Dependencies:** Phase 11 (core features complete before documentation)
**Requirements:** TBD
**Plans:** 0 plans
Plans:
- [ ] TBD (run /gsd:plan-phase 12 to break down)
**Success Criteria:**
[To be defined during planning]
---
## Progress
| Phase | Name | Milestone | Status |
|-------|------|-----------|--------|
| 1-5 | Foundation through Polish | v1.0 | Complete |
| 6 | n8n API Access | v1.1 | Complete |
| 7 | Socket Security | v1.1 | Complete |
| 8 | Inline Keyboard Infrastructure | v1.1 | Complete |
| 9 | Batch Operations | v1.1 | Complete |
| 10 | Workflow Modularization | v1.2 | Pending |
| 11 | Polish & Audit | v1.2 | Pending |
| 12 | Documentation Overhaul | v1.2 | Pending |
**v1.2 Coverage:** 4 requirements mapped (UNR-01, ENV-01, ENV-02, WEB-01), modularization TBD
---
*Updated: 2026-02-04 after v1.1 milestone*