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

Track payload sizing & spec presets (frontend/API-driven) #1

New Issue
Open
opened 2025-12-14 18:45:19 +00:00 by jester · 0 comments
jester commented 2025-12-14 18:45:19 +00:00
Owner
Copy Link

We need a project-level TODO to track how container sizing (CPU/RAM/Disk) is handled alongside payloads.

Current decision:

  • Do NOT add spec profiles to the DB yet
  • Use frontend/API preset payloads for sizing (Small/Medium/Large, etc.)
  • Apply sizing via Proxmox API at creation time
  • Agent remains unaware of sizing; payload focuses on behavior (game/dev, runtime, addons)

Future considerations:

  • Persist sizing intent/profile key in DB if billing, audit, or per-customer defaults are needed
  • Ensure preset definitions are centralized and documented

This belongs in zlh-grind as project architecture guidance, not zlh-agent-specific work.

We need a project-level TODO to track how container sizing (CPU/RAM/Disk) is handled alongside payloads. Current decision: - Do NOT add spec profiles to the DB yet - Use frontend/API preset payloads for sizing (Small/Medium/Large, etc.) - Apply sizing via Proxmox API at creation time - Agent remains unaware of sizing; payload focuses on behavior (game/dev, runtime, addons) Future considerations: - Persist sizing intent/profile key in DB if billing, audit, or per-customer defaults are needed - Ensure preset definitions are centralized and documented This belongs in zlh-grind as project architecture guidance, not zlh-agent-specific work.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: jester/zlh-grind#1
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?