b89f78db21
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>
1.8 KiB
1.8 KiB
Project Milestones: Unraid Docker Manager
v1.1 n8n Integration & Polish (Shipped: 2026-02-04)
Delivered: Inline keyboard UX and Docker security hardening — button-driven container control with filtered socket proxy.
Phases completed: 6-9 (11 plans total)
Key accomplishments:
- n8n API access for programmatic workflow management
- Docker socket proxy deployment removing direct socket exposure
- Inline keyboard with container list, pagination, and action buttons
- Batch operations with sequential execution and progress feedback
- Confirmation dialogs for dangerous actions (stop, update)
Stats:
- 38 files modified (+14,062/-4,239 lines)
- 8,485 lines of JSON workflow
- 4 phases, 11 plans
- 2 days (2026-02-03 → 2026-02-04)
Git range: 7e85697 → fa7c603
What's next: v1.2 with workflow modularization, webhook fix, environment audit, and documentation.
v1.0 Docker Control via Telegram (Shipped: 2026-02-02)
Delivered: Telegram bot for managing Docker containers on Unraid — status, start, stop, restart, update, logs via keyword commands.
Phases completed: 1-5 (12 plans total)
Key accomplishments:
- Telegram bot with keyword routing (no Claude API dependency)
- Docker socket integration via n8n with curl
- Container matching with exact-match priority
- Update command with image pull, recreate, old image cleanup
- Log viewing with configurable line counts
- Single-user auth via Telegram user ID
Stats:
- 2 files (n8n-workflow.json, README.md)
- ~3,400 lines of JSON workflow + markdown
- 5 phases, 12 plans
- 5 days from start to ship (2026-01-28 → 2026-02-02)
Git range: Initial commit → e5c02f9
What's next: Consider v1.1 with n8n API integration for faster development iteration, or additional features like resource monitoring.