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

docs: define milestone v1.4 requirements

Browse Source
This commit is contained in:
Lucas Berger
2026-02-09 08:11:54 -05:00
parent bab819f6c8
commit 7eab41eaba
2 changed files with 119 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.planning/PROJECT.md
+9 -4
View File
@@ -56,11 +56,12 @@ When you get a container update notification or notice a service is down, you ca
**Goal:** Replace Docker socket proxy with Unraid's GraphQL API for all container operations, remove all proxy artifacts, and update documentation.
**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)
- All container operations via Unraid GraphQL API (status, start, stop, restart, update)
- Remove container logs feature (not valuable enough to justify hybrid architecture)
- Remove docker-socket-proxy container entirely (no hybrid architecture)
- Remove all proxy-related artifacts from workflows, credentials, n8n container config
- Documentation fully updated for Unraid API-native architecture (README, ARCHITECTURE.md, CLAUDE.md)
- Migration/cleanup instructions for removing the proxy container
- Cleanup instructions for removing the proxy container
### Out of Scope
@@ -70,6 +71,8 @@ When you get a container update notification or notice a service is down, you ca
- Proactive monitoring/notifications — bot is reactive (you ask, it answers)
- Offline mode — real-time Docker API access is core to functionality
- Ring buffer / persistent debug logging — n8n static data is execution-scoped, not workflow-scoped
- Container logs via Telegram bot — removed in v1.4 to eliminate hybrid architecture (Docker proxy + Unraid API); not valuable enough to justify complexity
- Real-time container stats — requires WebSocket infrastructure, defer to future
## Current State
@@ -132,6 +135,8 @@ When you get a container update notification or notice a service is down, you ca
| myunraid.net cloud relay for Unraid API | Direct LAN IP fails (nginx strips auth headers on redirect) | ✓ Good |
| Environment variables for Unraid API auth | More reliable than n8n Header Auth credential system for GraphQL | ✓ Good |
| Descope v1.3 to Phase 14 only | Phases 15-16 superseded by v1.4 Unraid API Native approach | ✓ Good |
| Remove container logs feature in v1.4 | Not valuable enough to justify hybrid architecture (Docker proxy for logs + Unraid API for everything else) | — Pending |
| Remove docker-socket-proxy entirely | Clean single-API architecture, no hybrid routing complexity | — Pending |
---
*Last updated: 2026-02-09 after v1.4 milestone started*