Update documentation for app info pages feature
- CONTEXT.md: session 5 with app detail/info pages + optional config - README.md: add optional-config API endpoint, update version to 0.2.11 - CLAUDE.md: add app info page patterns to key patterns section Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -24,7 +24,7 @@ controller generates secrets, saves app.yaml, runs `docker compose up -d`, and t
|
||||
with Traefik routing and health checks. The dashboard correctly shows real-time container states
|
||||
including health substatus (starting → healthy → running).
|
||||
|
||||
Current version: **v0.2.1**
|
||||
Current version: **v0.2.111**
|
||||
|
||||
### What works
|
||||
- Dashboard with live container state (green/orange/yellow/red)
|
||||
@@ -32,6 +32,8 @@ Current version: **v0.2.1**
|
||||
- Stack operations: start, stop, restart, update (pull + recreate)
|
||||
- Live-scrolling log viewer with auto-refresh (3s polling), pause/resume, and scroll position tracking
|
||||
- Deploy page doubles as config viewer (read-only mode for deployed apps)
|
||||
- App detail/info pages with use cases, setup guide, screenshots, and optional config
|
||||
- Optional config saves to `app.yaml` and restarts deployed apps (e.g., metadata provider API keys)
|
||||
- Periodic stack rescanning (every 2 minutes)
|
||||
- Manual rescan endpoint (`POST /api/stacks/rescan`)
|
||||
- Alphabetically sorted stack display (consistent card ordering)
|
||||
@@ -42,7 +44,7 @@ Current version: **v0.2.1**
|
||||
- Memory summary bar shown on deploy page before deployment
|
||||
- Felhom.eu logo SVG in sidebar and login page
|
||||
- Verbose debug logging with operation timing, post-start container state checks, and image pull detection
|
||||
- Clickable app cards on dashboard and applications pages (navigate to detail/deploy page)
|
||||
- Clickable app cards on dashboard and applications pages (navigate to info page)
|
||||
- Memory bar with two-segment visualization on deploy page (committed vs new app allocation)
|
||||
- Deployment progress UI: 3-step progress panel with real-time health polling (config → containers → health check)
|
||||
|
||||
@@ -321,17 +323,17 @@ See `docs/BUILDING.md` for the full guide.
|
||||
```bash
|
||||
# Quick build (current platform only)
|
||||
cd ~/build/felhom-controller
|
||||
./build.sh 0.2.1
|
||||
./build.sh 0.2.11
|
||||
|
||||
# Build + push to Gitea registry
|
||||
./build.sh 0.2.1 --push
|
||||
./build.sh 0.2.11 --push
|
||||
```
|
||||
|
||||
### Deploy on customer node
|
||||
|
||||
```bash
|
||||
# Pull new image
|
||||
docker pull gitea.dooplex.hu/admin/felhom-controller:0.2.1
|
||||
docker pull gitea.dooplex.hu/admin/felhom-controller:0.2.11
|
||||
|
||||
# IMPORTANT: use 'up -d', NOT 'restart' — restart doesn't pick up new images
|
||||
cd /opt/docker/felhom-controller
|
||||
@@ -342,7 +344,7 @@ docker compose up -d
|
||||
|
||||
| Node | Hardware | Domain | IP | Status |
|
||||
|------|----------|--------|----|--------|
|
||||
| demo-felhom | Acemagic GK3PLUS N100, 16G RAM, 512G SSD + 1TB HDD | demo-felhom.eu | 192.168.0.162 | ✅ Controller v0.2.1 + Paperless-ngx running |
|
||||
| demo-felhom | Acemagic GK3PLUS N100, 16G RAM, 512G SSD + 1TB HDD | demo-felhom.eu | 192.168.0.162 | ✅ Controller v0.2.11 + Paperless-ngx running |
|
||||
| pi-customer-1 | Raspberry Pi 3B+, 1G RAM, 32G SD | pi-customer-1.local | — | 📲 Not yet tested |
|
||||
|
||||
### First deployment log (Paperless-ngx on demo-felhom)
|
||||
@@ -372,6 +374,7 @@ docker compose up -d
|
||||
| POST | `/api/stacks/{name}/stop` | Yes | Stop stack (not protected) |
|
||||
| POST | `/api/stacks/{name}/restart` | Yes | Restart stack |
|
||||
| POST | `/api/stacks/{name}/update` | Yes | Pull images + recreate |
|
||||
| POST | `/api/stacks/{name}/optional-config` | Yes | Update optional config env vars |
|
||||
| GET | `/api/stacks/{name}/logs` | Yes | Container logs (add `?raw=1` for plain text) |
|
||||
| POST | `/api/stacks/rescan` | Yes | Trigger manual stack discovery |
|
||||
| GET | `/api/system/info` | Yes | System resource usage (RAM, disk, HDD) |
|
||||
|
||||
Reference in New Issue
Block a user