luckberg/unraid-docker-manager
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: start milestone v1.4 Unraid API Native

Browse Source
This commit is contained in:
Lucas Berger
2026-02-09 07:52:53 -05:00
parent 903e73d616
commit bb47664188
2 changed files with 19 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.planning/PROJECT.md
+12 -6
View File
@@ -51,11 +51,16 @@ When you get a container update notification or notice a service is down, you ca
### Active ### Active
**v1.4: Unraid API Native (planned)** ## Current Milestone: v1.4 Unraid API Native
- [ ] Replace Docker socket proxy with Unraid GraphQL API for all container operations
- [ ] Remove docker-socket-proxy container dependency **Goal:** Replace Docker socket proxy with Unraid's GraphQL API for all container operations, remove all proxy artifacts, and update documentation.
- [ ] Container updates via Unraid API (naturally resolves badge sync problem)
- [ ] Documentation covers full Unraid API setup and migration **Target features:**
- All container operations via Unraid GraphQL API (status, start, stop, restart, update, logs)
- Remove docker-socket-proxy references from workflows, credentials, and n8n container config
- Clean up all proxy-related artifacts (nodes, variables, network references)
- Documentation fully updated for Unraid API-native architecture (README, ARCHITECTURE.md, CLAUDE.md)
- Migration/cleanup instructions for removing the proxy container
### Out of Scope ### Out of Scope
@@ -69,6 +74,7 @@ When you get a container update notification or notice a service is down, you ca
## Current State ## Current State
**Shipped:** v1.3 (2026-02-09) **Shipped:** v1.3 (2026-02-09)
**Building:** v1.4 Unraid API Native
**Tech stack:** n8n workflow + Telegram Bot API + Docker socket proxy + Unraid GraphQL API **Tech stack:** n8n workflow + Telegram Bot API + Docker socket proxy + Unraid GraphQL API
**Architecture:** 1 main workflow (169 nodes) + 7 sub-workflows (121 nodes) = 290 total nodes **Architecture:** 1 main workflow (169 nodes) + 7 sub-workflows (121 nodes) = 290 total nodes
**Files:** 8 workflow JSON files (~11K LOC), README.md, ARCHITECTURE.md **Files:** 8 workflow JSON files (~11K LOC), README.md, ARCHITECTURE.md
@@ -128,4 +134,4 @@ When you get a container update notification or notice a service is down, you ca
| Descope v1.3 to Phase 14 only | Phases 15-16 superseded by v1.4 Unraid API Native approach | ✓ Good | | Descope v1.3 to Phase 14 only | Phases 15-16 superseded by v1.4 Unraid API Native approach | ✓ Good |
--- ---
*Last updated: 2026-02-09 after v1.3 milestone shipped* *Last updated: 2026-02-09 after v1.4 milestone started*
.planning/STATE.md
+7 -6
View File
@@ -2,9 +2,10 @@
## Current Position ## Current Position
- **Milestone:** v1.3 Unraid Update Status Sync — SHIPPED - **Milestone:** v1.4 Unraid API Native
- **Status:** Milestone complete, planning next milestone - **Phase:** Not started (defining requirements)
- **Last activity:** 2026-02-09 -- Shipped v1.3 (descoped to Phase 14) - **Status:** Defining requirements
- **Last activity:** 2026-02-09 — Milestone v1.4 started
## Project Reference ## Project Reference
@@ -12,7 +13,7 @@ See: .planning/PROJECT.md (updated 2026-02-09)
**Core value:** When you get a container update notification or notice a service is down, you can immediately investigate and act from your phone. **Core value:** When you get a container update notification or notice a service is down, you can immediately investigate and act from your phone.
**Current focus:** Planning v1.4 — Unraid API Native (replace Docker socket proxy with Unraid GraphQL API) **Current focus:** v1.4 Unraid API Native — replace Docker socket proxy with Unraid GraphQL API
## Progress ## Progress
@@ -75,8 +76,8 @@ None.
## Session Continuity ## Session Continuity
Last session: 2026-02-09 Last session: 2026-02-09
Stopped at: Shipped v1.3 milestone Stopped at: Starting v1.4 milestone
Next step: /gsd:new-milestone for v1.4 Unraid API Native Next step: Research → Requirements → Roadmap
--- ---
*Auto-maintained by GSD workflow* *Auto-maintained by GSD workflow*