The form opened with the four main versions already ticked, so the plan showed four VMs nobody had asked for. F5 on an untouched form would have created them. Deploying is expensive and hard to undo — the list now starts empty and the choice is made, not inherited. The « * » still marks each distro's main version, and F7 ticks exactly those four in one keystroke, so nothing is lost but the presumption. With an empty list a « 0 VM · 0 vCPU » total teaches nothing, so the footer says what to do instead: tick what to deploy, F7 main versions, F6 all. Verified headless: no box ticked on open, F5 producing no spec at all, F7 giving back the four, and the ticks surviving a switch to « all architectures » (4 of 30) since identity is distro/version/arch, not rank. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| database_manager.py | ||
| kdbx_manager.py | ||
| logo_ascii.txt | ||
| qemu_deploy_form.py | ||
| qemu_install_monitor.py | ||
| README.base.md | ||
| README.fr.md | ||
| README.md | ||
| source_todo.sh | ||
| todo.json | ||
| todo.py | ||
| todo_example.json | ||
| todo_file_browser.py | ||
| todo_i18n.py | ||
| todo_prefs.py | ||
| todo_telemetry.py | ||
| todo_upgrade.py | ||
| version_manager.py | ||
TODO is an assistant robot to use ERPLibre
Execute it with ./script/todo/todo.py or make todo.
For a new project, copy todo_example.json to private/todo/todo_override.json | private/todo/todo_override_private.json and edit it.