jester/zlh-grind
1
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases Wiki Activity

Add code-server memory concern, Velocity resync gap, migration complete to closed threads

Browse Source
This commit is contained in:
jester 2026-04-04 16:37:08 +00:00
parent 72ce0b0525
commit e9d0d67d36
1 changed files with 27 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
OPEN_THREADS.md
View File

@ -56,6 +56,14 @@ Confirmed:
- detection via `/proc/*/cmdline` scan
- full browser IDE loading confirmed at `dev-6070.zerolaghub.dev`
**Outstanding — Memory concern:**
- code-server consumes 1-2GB RAM at idle
- observed 99% memory usage in dev container during active use with AI coding agent
- 8GB container allocation may be insufficient for heavy dev workloads
- need to establish baseline memory usage for code-server alone vs with active coding session
- consider raising default dev container RAM or making it tier-based
- **stress test: k6 IDE session load test** — still outstanding from pre-launch checklist
---
### Game Server Supervision
@ -115,7 +123,7 @@ Current state:
---
## API (zpack-api)
## API (zpac-api)
Completed:
@ -137,10 +145,11 @@ Outstanding:
- simplify and harden host-native `devProxy`
- dev runtime catalog endpoint for portal
- Headscale auth key generation
- **Velocity resync endpoint** — `POST /api/velocity/resync` to re-register all running containers after Velocity restart
---
## Portal (zpack-portal)
## Portal (zpac-portal)
Completed:
@ -157,7 +166,7 @@ Outstanding:
- SSH config snippet for power users (optional, clearly labeled as requiring cloudflared install)
- **User onboarding flow** — what happens after registration? Guided first-server creation needed
- **Email notifications** — server crashed, provisioning complete, billing receipts
- Remove `testdameon` binary from repo root (7MB, should not be in repo)
- Remove `testdaemon` binary from repo root (7MB, should not be in repo)
---
@ -170,6 +179,17 @@ Outstanding:
---
## Velocity / ZpackVelocityBridge
Outstanding:
- **Server registrations are in-memory only** — lost on Velocity restart. API needs `POST /api/velocity/resync` to re-register all running containers
- **ZpackCommands not registered** — `/zpack status/list/reload` commands exist in code but not wired up
- **Player routing on restart** — existing running containers go unrouted until new provisioning happens or resync is called
- See `SCRATCH/velocity-plugin.md` for full plugin documentation
---
## Infrastructure
### Hosting — GTHost (Decision: Stay, Most Cost-Effective)
@ -211,11 +231,9 @@ Outstanding before launch:
- **Email notifications** — crashed, billing, provisioning
- **Upload testing** — test file upload flow end-to-end in dev containers
- **Billing endpoints** — add back to API
- **Stress testing** — k6 IDE session load test + Minecraft bot test
- **Stress testing** — k6 IDE session load test + Minecraft bot test + **code-server memory baseline**
- **OPNsense audit** — both routers need systematic validation
- **Dedicated host upgrade** — evaluate GTHost Gold 6152, Detroit
- Trial period: $5/day up to 10 days, PBS restore approach
- Remove `testdameon` binary from zpack-portal repo root
- Remove `testdaemon` binary from zpac-portal repo root
---
@ -256,3 +274,5 @@ Future work:
- ✅ Portal copy rewrite — landing, features, FAQ, about, pricing
- ✅ DDoS investigation — minimal attack surface, Velocity proxy + internal architecture, accepted risk
- ✅ Hosting provider decision — GTHost Detroit, most cost-effective option
- ✅ Migration to Detroit — complete Apr 2, 2026
- ✅ Internal FQDN migration — all services on internal.zlh