Dilshod Rasulov 1a17ceed82 fix(sync): store VM memory/disk in MB/GB, not raw Proxmox bytes ...

The monitoring worker wrote Proxmox maxmem/maxdisk (bytes) straight into
the memory/disk_size columns, which the rest of the app stores as MB/GB.
Every sync cycle clobbered correct values with bytes, so the saved-config
card showed huge byte numbers under MB/GB labels. Convert via new
_bytes_to_mb/_bytes_to_gb helpers; existing rows self-heal on next sync.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-22 02:42:49 +05:00

..

__init__.py

Add complete project structure and all files

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

monitoring_worker.py

fix(sync): store VM memory/disk in MB/GB, not raw Proxmox bytes

2026-06-22 02:42:49 +05:00