phg/pve-vm-setup
0
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Initial working version

Browse source
This commit is contained in:
Philip Henning 2026-03-08 18:32:25 +01:00
parent 34a0627e76
commit b6886cb34a
61 changed files with 4475 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

5
ARCHITECTURE.md
View file

@ -108,7 +108,7 @@ Expected responsibilities:
- provide shared app context to screens
- coordinate back/next/confirm navigation
The current run command placeholder in `README.md` and `TASKS.md` is `uv run python -m your_app`, so the real package/module name is still unresolved.
The current run command in `README.md` and `TASKS.md` is `uv run python -m pve_vm_setup`.
### 2. Screens
@ -357,7 +357,7 @@ The create-then-configure request sequence is especially important to cover in s
`TASKS.md` does not prescribe exact paths, but it does require a separation of concerns. A structure consistent with the current requirements would be:
```text
your_app/
pve_vm_setup/
__main__.py
app.py
screens/
@ -392,7 +392,6 @@ These defaults are central enough to architecture because they belong in domain/
The available resources leave several architectural details unresolved:
- What concrete Python package/module name should replace `your_app`?
- Which Proxmox authentication mechanism should be used under the hood: ticket/cookie, API token, or both?
- How should session persistence work across screens and retries?
- Does the app target a single Proxmox node/cluster endpoint or support multiple saved endpoints?