Files
unraid-docker-manager/.planning/ROADMAP.md
T
Lucas Berger b89f78db21 chore: complete v1.1 milestone
Archived:
- milestones/v1.1-ROADMAP.md
- milestones/v1.1-REQUIREMENTS.md

Deleted (fresh for next milestone):
- REQUIREMENTS.md

Updated:
- MILESTONES.md (new v1.1 entry)
- PROJECT.md (requirements → Validated, updated current state)
- ROADMAP.md (v1.1 collapsed, v1.2 phases added)
- STATE.md (reset for v1.2)

v1.1 shipped: Inline keyboard UX and Docker security hardening
- Phases 6-9 complete (11 plans)
- 4 requirements deferred to v1.2 (UNR-01, ENV-01, ENV-02, WEB-01)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-02-04 10:55:26 -05:00

89 lines
2.5 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, and verify environment configuration
**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)
---
### 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*