markmorado a92cb0df33 fix(vms): auto-stop running VM/CT before destroy ...

The destroy endpoints returned 400 'Cannot delete a running container.
Stop it first.' when the user clicked Destroy on a running instance.
Since the destroy dialog already requires typing the instance name to
confirm, the action is unambiguously intentional — now both endpoints
issue stop_container/stop_vm with force=True, wait up to 15s for the
status to leave 'running', and only then proceed with deletion.

2026-05-06 21:11:15 +02:00

..

app

fix(vms): auto-stop running VM/CT before destroy

2026-05-06 21:11:15 +02:00

migrations

feat(vm-ops): make reinstall/clone/change-password async via DeployTask

2026-04-30 00:08:41 +02:00

tests

fix(reinstall): use OSTemplate.vmid (not template_vmid) and convert memory bytes->MB

2026-04-29 23:48:48 +02:00

.dockerignore

Add complete project structure and all files

2025-12-15 13:03:29 +05:00

.env.example

security: encrypt sensitive DB fields, clean up dynamic import

2026-03-06 16:17:45 +00:00

Dockerfile

fix: исправления и улучшения от 30.04.2026

2026-04-30 21:58:44 +02:00

init_admin.py

security: fix critical vulnerabilities and code quality issues

2026-03-06 15:57:20 +00:00

init_panel_settings.py

Add complete project structure and all files

2025-12-15 13:03:29 +05:00

pytest.ini

fix(reinstall): use OSTemplate.vmid (not template_vmid) and convert memory bytes->MB

2026-04-29 23:48:48 +02:00

requirements-dev.txt

fix(reinstall): use OSTemplate.vmid (not template_vmid) and convert memory bytes->MB

2026-04-29 23:48:48 +02:00

requirements.txt

Add complete project structure and all files

2025-12-15 13:03:29 +05:00

sign_logo.py

Add complete project structure and all files

2025-12-15 13:03:29 +05:00