Files
unraid-docker-manager/.planning/ROADMAP.md
T
Lucas Berger 186f11362e chore(10-05): verify and document workflow refactoring
- Run cleanup and verification script
- No orphaned nodes found
- Workflow structure validated
- Final node count: 199 (reduced from 209, -4.8%)
- Add comprehensive deployment guide

Node composition:
- 79 code nodes
- 50 httpRequest nodes
- 27 telegram nodes
- 14 if nodes
- 10 switch nodes
- 9 executeCommand nodes
- 9 executeWorkflow nodes (sub-workflow calls)
- 1 telegramTrigger node

Note: Node count (199) is above target range (120-150) but achieves
primary goals of eliminating duplicate logic. Further optimization
possible (~40-45 nodes) by consolidating batch UI and confirmation flows.

Deployment requires importing n8n-container-logs.json and updating
the workflow ID in main workflow Execute Text/Inline Logs nodes.
2026-02-04 13:58:48 -05:00

4.4 KiB

Roadmap — Unraid Docker Manager

Milestones

  • v1.0 Docker Control via Telegram — Phases 1-5 (shipped 2026-02-02) -> Archive
  • v1.1 n8n Integration & Polish — Phases 6-9 (shipped 2026-02-04) -> Archive
  • v1.2 Modularization & Polish — Phases 10-13 + 10.1 (planned)

v1.2: Modularization & Polish

Modularize the workflow for maintainability, add "update all" functionality, fix callback data limits, and polish remaining issues.

Phase 10: Workflow Modularization

Goal: Break main workflow into modular sub-workflows for maintainability

Dependencies: None

Requirements: MOD-01, MOD-02, DEBT-03

Plans: 5 plans

Plans:

  • 10-01-PLAN.md — Orphan node cleanup (removed 2 orphan nodes)
  • 10-02-PLAN.md — Extract container update sub-workflow (consolidates DEBT-03)
  • 10-03-PLAN.md — Extract container actions sub-workflow (start/stop/restart)
  • 10-04-PLAN.md — Integration verification and user checkpoint
  • 10-05-PLAN.md — Complete modularization (batch operations, logs sub-workflow)

Success Criteria:

  1. Workflow split into logical sub-workflows (update, actions, logs)
  2. Sub-workflows callable from main without code duplication
  3. Update flow consolidated between single and batch paths
  4. Actions flow consolidated between single and batch paths
  5. Main workflow reduced from 209 to ~120-140 nodes
  6. All existing functionality still works after modularization

Phase 10.1: Better Logging and Log Management (INSERTED)

Goal: Improve logging capabilities and log management features

Dependencies: Phase 10 (modularization complete)

Requirements: TBD

Plans: 0 plans

Plans:

  • TBD (run /gsd:plan-phase 10.1 to break down)

Success Criteria:

  1. [To be defined during planning]

Phase 11: Update All & Callback Limits

Goal: Add "update all" functionality and fix callback data limits for batch selection

Dependencies: Phase 10 (modularization provides cleaner base for new features)

Requirements: BATCH-04, BATCH-05, BATCH-06, BATCH-07

Plans: 0 plans

Plans:

  • TBD (run /gsd:plan-phase 11 to break down)

Success Criteria:

  1. User can type "update all" to update all :latest containers with confirmation
  2. User can tap "Update All" in inline keyboard to update all :latest containers
  3. Batch selection keyboard allows selecting 5+ containers without hitting callback limit
  4. Containers with long names (20+ chars) can be selected in batch keyboard

Phase 12: Polish & Audit

Goal: Clear Unraid update badges, verify environment configuration, and fix remaining tech debt

Dependencies: Phase 11 (features complete before polish)

Requirements: UNR-01, ENV-01, ENV-02, DEBT-02

Plans: 0 plans

Plans:

  • TBD (run /gsd:plan-phase 12 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. Image pull command has single --max-time flag (600s)

Phase 13: Documentation Overhaul

Goal: Update README and documentation to reflect current architecture and features

Dependencies: Phase 12 (core features complete before documentation)

Requirements: DEBT-01

Plans: 0 plans

Plans:

  • TBD (run /gsd:plan-phase 13 to break down)

Success Criteria:

  1. README documents docker-socket-proxy architecture (not direct socket mount)
  2. README documents all v1.2 features (update all, batch selection improvements)
  3. Setup instructions verified accurate for clean install

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 Planned
10.1 Better Logging and Log Management v1.2 Pending (INSERTED)
11 Update All & Callback Limits v1.2 Pending
12 Polish & Audit v1.2 Pending
13 Documentation Overhaul v1.2 Pending

v1.2 Coverage: 12+ requirements mapped across 5 phases


Updated: 2026-02-04 after Phase 10 planning