clonebox 0.1.9__tar.gz → 0.1.10__tar.gz

{clonebox-0.1.9/src/clonebox.egg-info → clonebox-0.1.10}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: clonebox
-Version: 0.1.9
+Version: 0.1.10
 Summary: Clone your workstation environment to an isolated VM with selective apps, paths and services
 Author: CloneBox Team
 License: Apache-2.0
@@ -64,6 +64,41 @@ CloneBox lets you create isolated virtual machines with only the applications, d
 - 🖥️ **GUI support** - SPICE graphics with virt-viewer integration
 - ⚡ **Fast creation** - No full disk cloning, VMs are ready in seconds
 - 📥 **Auto-download** - Automatically downloads and caches Ubuntu cloud images (stored in ~/Downloads)
+- 📊 **Health monitoring** - Built-in health checks for packages, services, and mounts
+- 🔄 **VM migration** - Export/import VMs with data between workstations
+- 🧪 **Configuration testing** - Validate VM settings and functionality
+- 📁 **App data sync** - Include browser profiles, IDE settings, and app configs
+
+
+
+
+CloneBox to narzędzie CLI do **szybkiego klonowania aktualnego środowiska workstation do izolowanej maszyny wirtualnej (VM)**. 
+Zamiast pełnego kopiowania dysku, używa **bind mounts** (udostępnianie katalogów na żywo) i **cloud-init** do selektywnego przeniesienia tylko potrzebnych elementów: uruchomionych usług (Docker, PostgreSQL, nginx), aplikacji, ścieżek projektów i konfiguracji. Automatycznie pobiera obrazy Ubuntu, instaluje pakiety i uruchamia VM z SPICE GUI. Idealne dla deweloperów na Linuxie – VM powstaje w minuty, bez duplikowania danych.
+
+Kluczowe komendy:
+- `clonebox` – interaktywny wizard (detect + create + start)
+- `clonebox detect` – skanuje usługi/apps/ścieżki
+- `clonebox clone . --user --run` – szybki klon bieżącego katalogu z użytkownikiem i autostartem
+
+### Dlaczego wirtualne klony workstation mają sens?
+
+**Problem**: Developerzy/Vibecoderzy nie izolują środowisk dev/test (np. dla AI agentów), bo ręczne odtwarzanie setupu to ból – godziny na instalację apps, usług, configów, dotfiles. Przechodzenie z fizycznego PC na VM wymagałoby pełnego rebuilda, co blokuje workflow.
+
+**Rozwiązanie CloneBox**: Automatycznie **skanuje i klonuje stan "tu i teraz"** (usługi z `ps`, dockery z `docker ps`, projekty z git/.env). VM dziedziczy środowisko bez kopiowania całego śmietnika – tylko wybrane bind mounty. 
+
+**Korzyści w twoim kontekście (embedded/distributed systems, AI automation)**:
+- **Sandbox dla eksperymentów**: Testuj AI agenty, edge computing (RPi/ESP32 symulacje) czy Camel/ERP integracje w izolacji, bez psucia hosta.
+- **Reprodukcja workstation**: Na firmowym PC masz setup z domu (Python/Rust/Go envs, Docker compose, Postgres dev DB) – klonujesz i pracujesz identycznie.
+- **Szybkość > dotfiles**: Dotfiles odtwarzają configi, ale nie łapią runtime stanu (uruchomione serwery, otwarte projekty). CloneBox to "snapshot na sterydach".
+- **Bezpieczeństwo/cost-optymalizacja**: Izolacja od plików hosta (tylko mounts), zero downtime, tanie w zasobach (libvirt/QEMU). Dla SME: szybki onboarding dev env bez migracji fizycznej.
+- **AI-friendly**: Agenci LLMs (jak te z twoich hobby) mogą działać w VM z pełnym kontekstem, bez ryzyka "zasmiecania" main PC.
+
+Przykład: Masz uruchomiony Kubernetes Podman z twoim home labem + projekt automotive leasing. `clonebox clone ~/projects --run` → VM gotowa w 30s, z tymi samymi serwisami, ale izolowana. Lepsze niż Docker (brak GUI/full OS) czy pełna migracja.
+
+**Dlaczego ludzie tego nie robią?** Brak automatyzacji – nikt nie chce ręcznie rebuildować. 
+- CloneBox rozwiązuje to jednym poleceniem. Super match dla twoich interesów (distributed infra, AI tools, business automation).
+
+
 
 ## Installation
 
@@ -142,7 +177,6 @@ Simply run `clonebox` to start the interactive wizard:
 ```bash
 clonebox
 clonebox clone . --user --run --replace --base-image ~/ubuntu-22.04-cloud.qcow2
-
 ```
 
 The wizard will:
@@ -181,6 +215,130 @@ clonebox detect --json
 
 ## Usage Examples
 
+### Basic Workflow
+
+```bash
+# 1. Clone current directory with auto-detection
+clonebox clone . --user
+
+# 2. Review generated config
+cat .clonebox.yaml
+
+# 3. Create and start VM
+clonebox start . --user --viewer
+
+# 4. Check VM status
+clonebox status . --user
+
+# 5. Open VM window later
+clonebox open . --user
+
+# 6. Stop VM when done
+clonebox stop . --user
+```
+
+### Development Environment with Browser Profiles
+
+```bash
+# Clone with app data (browser profiles, IDE settings)
+clonebox clone . --user --run
+
+# VM will have:
+# - All your project directories
+# - Browser profiles (Chrome, Firefox) with bookmarks and passwords
+# - IDE settings (PyCharm, VSCode)
+# - Docker containers and services
+
+# Access in VM:
+ls ~/.config/google-chrome  # Chrome profile
+ls ~/.mozilla/firefox       # Firefox profile
+ls ~/.config/JetBrains      # PyCharm settings
+```
+
+### Testing VM Configuration
+
+```bash
+# Quick test - basic checks
+clonebox test . --user --quick
+
+# Full test with verbose output
+clonebox test . --user --verbose
+
+# Test output shows:
+# ✅ VM is defined in libvirt
+# ✅ VM is running
+# ✅ VM has network access (IP: 192.168.122.89)
+# ✅ Cloud-init completed
+# ✅ All mount points accessible
+# ✅ Health check triggered
+```
+
+### VM Health Monitoring
+
+```bash
+# Check overall status
+clonebox status . --user
+
+# Output:
+# 📊 Checking VM status: clone-clonebox
+# ✅ VM State: running
+# ✅ VM has network access
+# ☁️ Cloud-init: Still running (packages installing)
+# 🏥 Health Check Status... ⏳ Health check not yet run
+
+# Trigger health check
+clonebox status . --user --health
+
+# View detailed health report in VM:
+# cat /var/log/clonebox-health.log
+```
+
+### Export/Import Workflow
+
+```bash
+# On workstation A - Export VM with all data
+clonebox export . --user --include-data -o my-dev-env.tar.gz
+
+# Transfer file to workstation B, then import
+clonebox import my-dev-env.tar.gz --user
+
+# Start VM on new workstation
+clonebox start . --user
+clonebox open . --user
+
+# VM includes:
+# - Complete disk image
+# - All browser profiles and settings
+# - Project files
+# - Docker images and containers
+```
+
+### Troubleshooting Common Issues
+
+```bash
+# If mounts are empty after reboot:
+clonebox status . --user  # Check VM status
+# Then in VM:
+sudo mount -a              # Remount all fstab entries
+
+# If browser profiles don't sync:
+rm .clonebox.yaml
+clonebox clone . --user --run --replace
+
+# If GUI doesn't open:
+clonebox open . --user     # Easiest way
+# or:
+virt-viewer --connect qemu:///session clone-clonebox
+
+# Check VM details:
+clonebox list              # List all VMs
+virsh --connect qemu:///session dominfo clone-clonebox
+```
+
+## Legacy Examples (Manual Config)
+
+These examples use the older `create` command with manual JSON config. For most users, the `clone` command with auto-detection is easier.
+
 ### Python Development Environment
 
 ```bash
@@ -222,17 +380,36 @@ clonebox create --name fullstack --config '{
 
 ## Inside the VM
 
-After the VM boots, mount shared directories:
+After the VM boots, shared directories are automatically mounted via fstab entries. You can check their status:
 
 ```bash
-# Mount shared paths (9p filesystem)
-sudo mkdir -p /mnt/projects
-sudo mount -t 9p -o trans=virtio,version=9p2000.L mount0 /mnt/projects
+# Check mount status
+mount | grep 9p
 
-# Or add to /etc/fstab for permanent mount
-echo "mount0 /mnt/projects 9p trans=virtio,version=9p2000.L 0 0" | sudo tee -a /etc/fstab
+# View health check report
+cat /var/log/clonebox-health.log
+
+# Re-run health check manually
+clonebox-health
+
+# Check cloud-init status
+sudo cloud-init status
+
+# Manual mount (if needed)
+sudo mkdir -p /mnt/projects
+sudo mount -t 9p -o trans=virtio,version=9p2000.L,nofail mount0 /mnt/projects
 ```
 
+### Health Check System
+
+CloneBox includes automated health checks that verify:
+- Package installation (apt/snap)
+- Service status
+- Mount points accessibility
+- GUI readiness
+
+Health check logs are saved to `/var/log/clonebox-health.log` with a summary in `/var/log/clonebox-health-status`.
+
 ## Architecture
 
 ```
@@ -399,6 +576,7 @@ clonebox clone . --network auto
 | `clonebox clone . --network user` | Use user-mode networking (slirp) |
 | `clonebox clone . --network auto` | Auto-detect network mode (default) |
 | `clonebox start .` | Start VM from `.clonebox.yaml` in current dir |
+| `clonebox start . --viewer` | Start VM and open GUI window |
 | `clonebox start <name>` | Start existing VM by name |
 | `clonebox stop <name>` | Stop a VM (graceful shutdown) |
 | `clonebox stop -f <name>` | Force stop a VM |
@@ -408,6 +586,14 @@ clonebox clone . --network auto
 | `clonebox detect --yaml` | Output as YAML config |
 | `clonebox detect --yaml --dedupe` | YAML with duplicates removed |
 | `clonebox detect --json` | Output as JSON |
+| `clonebox status . --user` | Check VM health, cloud-init status, and IP address |
+| `clonebox test . --user` | Test VM configuration and validate all settings |
+| `clonebox export . --user` | Export VM for migration to another workstation |
+| `clonebox export . --user --include-data` | Export VM with browser profiles and configs |
+| `clonebox import archive.tar.gz --user` | Import VM from export archive |
+| `clonebox open . --user` | Open GUI viewer for VM (same as virt-viewer) |
+| `virt-viewer --connect qemu:///session <vm>` | Open GUI for running VM |
+| `virsh --connect qemu:///session console <vm>` | Open text console (Ctrl+] to exit) |
 
 ## Requirements
 
@@ -479,6 +665,102 @@ sudo apt install virt-viewer
 virt-viewer --connect qemu:///session <vm-name>
 ```
 
+### Browser Profiles Not Syncing
+
+If browser profiles or app data aren't available:
+
+1. **Regenerate config with app data:**
+   ```bash
+   rm .clonebox.yaml
+   clonebox clone . --user --run --replace
+   ```
+
+2. **Check mount permissions in VM:**
+   ```bash
+   # Verify mounts are accessible
+   ls -la ~/.config/google-chrome
+   ls -la ~/.mozilla/firefox
+   ```
+
+### Mount Points Empty After Reboot
+
+If shared directories appear empty after VM restart:
+
+1. **Check fstab entries:**
+   ```bash
+   cat /etc/fstab | grep 9p
+   ```
+
+2. **Mount manually:**
+   ```bash
+   sudo mount -a
+   ```
+
+3. **Verify access mode:**
+   - VMs created with `accessmode="mapped"` allow any user to access mounts
+   - Older VMs used `accessmode="passthrough"` which preserves host UIDs
+
+## Advanced Usage
+
+### VM Migration Between Workstations
+
+Export your complete VM environment:
+
+```bash
+# Export VM with all data
+clonebox export . --user --include-data -o my-dev-env.tar.gz
+
+# Transfer to new workstation, then import
+clonebox import my-dev-env.tar.gz --user
+clonebox start . --user
+```
+
+### Testing VM Configuration
+
+Validate your VM setup:
+
+```bash
+# Quick test (basic checks)
+clonebox test . --user --quick
+
+# Full test (includes health checks)
+clonebox test . --user --verbose
+```
+
+### Monitoring VM Health
+
+Check VM status from workstation:
+
+```bash
+# Check VM state, IP, cloud-init, and health
+clonebox status . --user
+
+# Trigger health check in VM
+clonebox status . --user --health
+```
+
+### Reopening VM Window
+
+If you close the VM window, you can reopen it:
+
+```bash
+# Open GUI viewer (easiest)
+clonebox open . --user
+
+# Start VM and open GUI (if VM is stopped)
+clonebox start . --user --viewer
+
+# Open GUI for running VM
+virt-viewer --connect qemu:///session clone-clonebox
+
+# List VMs to get the correct name
+clonebox list
+
+# Text console (no GUI)
+virsh --connect qemu:///session console clone-clonebox
+# Press Ctrl + ] to exit console
+```
+
 ## License
 
 MIT License - see [LICENSE](LICENSE) file.

{clonebox-0.1.9 → clonebox-0.1.10}/README.md

@@ -25,6 +25,41 @@ CloneBox lets you create isolated virtual machines with only the applications, d
 - 🖥️ **GUI support** - SPICE graphics with virt-viewer integration
 - ⚡ **Fast creation** - No full disk cloning, VMs are ready in seconds
 - 📥 **Auto-download** - Automatically downloads and caches Ubuntu cloud images (stored in ~/Downloads)
+- 📊 **Health monitoring** - Built-in health checks for packages, services, and mounts
+- 🔄 **VM migration** - Export/import VMs with data between workstations
+- 🧪 **Configuration testing** - Validate VM settings and functionality
+- 📁 **App data sync** - Include browser profiles, IDE settings, and app configs
+
+
+
+
+CloneBox to narzędzie CLI do **szybkiego klonowania aktualnego środowiska workstation do izolowanej maszyny wirtualnej (VM)**. 
+Zamiast pełnego kopiowania dysku, używa **bind mounts** (udostępnianie katalogów na żywo) i **cloud-init** do selektywnego przeniesienia tylko potrzebnych elementów: uruchomionych usług (Docker, PostgreSQL, nginx), aplikacji, ścieżek projektów i konfiguracji. Automatycznie pobiera obrazy Ubuntu, instaluje pakiety i uruchamia VM z SPICE GUI. Idealne dla deweloperów na Linuxie – VM powstaje w minuty, bez duplikowania danych.
+
+Kluczowe komendy:
+- `clonebox` – interaktywny wizard (detect + create + start)
+- `clonebox detect` – skanuje usługi/apps/ścieżki
+- `clonebox clone . --user --run` – szybki klon bieżącego katalogu z użytkownikiem i autostartem
+
+### Dlaczego wirtualne klony workstation mają sens?
+
+**Problem**: Developerzy/Vibecoderzy nie izolują środowisk dev/test (np. dla AI agentów), bo ręczne odtwarzanie setupu to ból – godziny na instalację apps, usług, configów, dotfiles. Przechodzenie z fizycznego PC na VM wymagałoby pełnego rebuilda, co blokuje workflow.
+
+**Rozwiązanie CloneBox**: Automatycznie **skanuje i klonuje stan "tu i teraz"** (usługi z `ps`, dockery z `docker ps`, projekty z git/.env). VM dziedziczy środowisko bez kopiowania całego śmietnika – tylko wybrane bind mounty. 
+
+**Korzyści w twoim kontekście (embedded/distributed systems, AI automation)**:
+- **Sandbox dla eksperymentów**: Testuj AI agenty, edge computing (RPi/ESP32 symulacje) czy Camel/ERP integracje w izolacji, bez psucia hosta.
+- **Reprodukcja workstation**: Na firmowym PC masz setup z domu (Python/Rust/Go envs, Docker compose, Postgres dev DB) – klonujesz i pracujesz identycznie.
+- **Szybkość > dotfiles**: Dotfiles odtwarzają configi, ale nie łapią runtime stanu (uruchomione serwery, otwarte projekty). CloneBox to "snapshot na sterydach".
+- **Bezpieczeństwo/cost-optymalizacja**: Izolacja od plików hosta (tylko mounts), zero downtime, tanie w zasobach (libvirt/QEMU). Dla SME: szybki onboarding dev env bez migracji fizycznej.
+- **AI-friendly**: Agenci LLMs (jak te z twoich hobby) mogą działać w VM z pełnym kontekstem, bez ryzyka "zasmiecania" main PC.
+
+Przykład: Masz uruchomiony Kubernetes Podman z twoim home labem + projekt automotive leasing. `clonebox clone ~/projects --run` → VM gotowa w 30s, z tymi samymi serwisami, ale izolowana. Lepsze niż Docker (brak GUI/full OS) czy pełna migracja.
+
+**Dlaczego ludzie tego nie robią?** Brak automatyzacji – nikt nie chce ręcznie rebuildować. 
+- CloneBox rozwiązuje to jednym poleceniem. Super match dla twoich interesów (distributed infra, AI tools, business automation).
+
+
 
 ## Installation
 
@@ -103,7 +138,6 @@ Simply run `clonebox` to start the interactive wizard:
 ```bash
 clonebox
 clonebox clone . --user --run --replace --base-image ~/ubuntu-22.04-cloud.qcow2
-
 ```
 
 The wizard will:
@@ -142,6 +176,130 @@ clonebox detect --json
 
 ## Usage Examples
 
+### Basic Workflow
+
+```bash
+# 1. Clone current directory with auto-detection
+clonebox clone . --user
+
+# 2. Review generated config
+cat .clonebox.yaml
+
+# 3. Create and start VM
+clonebox start . --user --viewer
+
+# 4. Check VM status
+clonebox status . --user
+
+# 5. Open VM window later
+clonebox open . --user
+
+# 6. Stop VM when done
+clonebox stop . --user
+```
+
+### Development Environment with Browser Profiles
+
+```bash
+# Clone with app data (browser profiles, IDE settings)
+clonebox clone . --user --run
+
+# VM will have:
+# - All your project directories
+# - Browser profiles (Chrome, Firefox) with bookmarks and passwords
+# - IDE settings (PyCharm, VSCode)
+# - Docker containers and services
+
+# Access in VM:
+ls ~/.config/google-chrome  # Chrome profile
+ls ~/.mozilla/firefox       # Firefox profile
+ls ~/.config/JetBrains      # PyCharm settings
+```
+
+### Testing VM Configuration
+
+```bash
+# Quick test - basic checks
+clonebox test . --user --quick
+
+# Full test with verbose output
+clonebox test . --user --verbose
+
+# Test output shows:
+# ✅ VM is defined in libvirt
+# ✅ VM is running
+# ✅ VM has network access (IP: 192.168.122.89)
+# ✅ Cloud-init completed
+# ✅ All mount points accessible
+# ✅ Health check triggered
+```
+
+### VM Health Monitoring
+
+```bash
+# Check overall status
+clonebox status . --user
+
+# Output:
+# 📊 Checking VM status: clone-clonebox
+# ✅ VM State: running
+# ✅ VM has network access
+# ☁️ Cloud-init: Still running (packages installing)
+# 🏥 Health Check Status... ⏳ Health check not yet run
+
+# Trigger health check
+clonebox status . --user --health
+
+# View detailed health report in VM:
+# cat /var/log/clonebox-health.log
+```
+
+### Export/Import Workflow
+
+```bash
+# On workstation A - Export VM with all data
+clonebox export . --user --include-data -o my-dev-env.tar.gz
+
+# Transfer file to workstation B, then import
+clonebox import my-dev-env.tar.gz --user
+
+# Start VM on new workstation
+clonebox start . --user
+clonebox open . --user
+
+# VM includes:
+# - Complete disk image
+# - All browser profiles and settings
+# - Project files
+# - Docker images and containers
+```
+
+### Troubleshooting Common Issues
+
+```bash
+# If mounts are empty after reboot:
+clonebox status . --user  # Check VM status
+# Then in VM:
+sudo mount -a              # Remount all fstab entries
+
+# If browser profiles don't sync:
+rm .clonebox.yaml
+clonebox clone . --user --run --replace
+
+# If GUI doesn't open:
+clonebox open . --user     # Easiest way
+# or:
+virt-viewer --connect qemu:///session clone-clonebox
+
+# Check VM details:
+clonebox list              # List all VMs
+virsh --connect qemu:///session dominfo clone-clonebox
+```
+
+## Legacy Examples (Manual Config)
+
+These examples use the older `create` command with manual JSON config. For most users, the `clone` command with auto-detection is easier.
+
 ### Python Development Environment
 
 ```bash
@@ -183,17 +341,36 @@ clonebox create --name fullstack --config '{
 
 ## Inside the VM
 
-After the VM boots, mount shared directories:
+After the VM boots, shared directories are automatically mounted via fstab entries. You can check their status:
 
 ```bash
-# Mount shared paths (9p filesystem)
-sudo mkdir -p /mnt/projects
-sudo mount -t 9p -o trans=virtio,version=9p2000.L mount0 /mnt/projects
+# Check mount status
+mount | grep 9p
 
-# Or add to /etc/fstab for permanent mount
-echo "mount0 /mnt/projects 9p trans=virtio,version=9p2000.L 0 0" | sudo tee -a /etc/fstab
+# View health check report
+cat /var/log/clonebox-health.log
+
+# Re-run health check manually
+clonebox-health
+
+# Check cloud-init status
+sudo cloud-init status
+
+# Manual mount (if needed)
+sudo mkdir -p /mnt/projects
+sudo mount -t 9p -o trans=virtio,version=9p2000.L,nofail mount0 /mnt/projects
 ```
 
+### Health Check System
+
+CloneBox includes automated health checks that verify:
+- Package installation (apt/snap)
+- Service status
+- Mount points accessibility
+- GUI readiness
+
+Health check logs are saved to `/var/log/clonebox-health.log` with a summary in `/var/log/clonebox-health-status`.
+
 ## Architecture
 
 ```
@@ -360,6 +537,7 @@ clonebox clone . --network auto
 | `clonebox clone . --network user` | Use user-mode networking (slirp) |
 | `clonebox clone . --network auto` | Auto-detect network mode (default) |
 | `clonebox start .` | Start VM from `.clonebox.yaml` in current dir |
+| `clonebox start . --viewer` | Start VM and open GUI window |
 | `clonebox start <name>` | Start existing VM by name |
 | `clonebox stop <name>` | Stop a VM (graceful shutdown) |
 | `clonebox stop -f <name>` | Force stop a VM |
@@ -369,6 +547,14 @@ clonebox clone . --network auto
 | `clonebox detect --yaml` | Output as YAML config |
 | `clonebox detect --yaml --dedupe` | YAML with duplicates removed |
 | `clonebox detect --json` | Output as JSON |
+| `clonebox status . --user` | Check VM health, cloud-init status, and IP address |
+| `clonebox test . --user` | Test VM configuration and validate all settings |
+| `clonebox export . --user` | Export VM for migration to another workstation |
+| `clonebox export . --user --include-data` | Export VM with browser profiles and configs |
+| `clonebox import archive.tar.gz --user` | Import VM from export archive |
+| `clonebox open . --user` | Open GUI viewer for VM (same as virt-viewer) |
+| `virt-viewer --connect qemu:///session <vm>` | Open GUI for running VM |
+| `virsh --connect qemu:///session console <vm>` | Open text console (Ctrl+] to exit) |
 
 ## Requirements
 
@@ -440,6 +626,102 @@ sudo apt install virt-viewer
 virt-viewer --connect qemu:///session <vm-name>
 ```
 
+### Browser Profiles Not Syncing
+
+If browser profiles or app data aren't available:
+
+1. **Regenerate config with app data:**
+   ```bash
+   rm .clonebox.yaml
+   clonebox clone . --user --run --replace
+   ```
+
+2. **Check mount permissions in VM:**
+   ```bash
+   # Verify mounts are accessible
+   ls -la ~/.config/google-chrome
+   ls -la ~/.mozilla/firefox
+   ```
+
+### Mount Points Empty After Reboot
+
+If shared directories appear empty after VM restart:
+
+1. **Check fstab entries:**
+   ```bash
+   cat /etc/fstab | grep 9p
+   ```
+
+2. **Mount manually:**
+   ```bash
+   sudo mount -a
+   ```
+
+3. **Verify access mode:**
+   - VMs created with `accessmode="mapped"` allow any user to access mounts
+   - Older VMs used `accessmode="passthrough"` which preserves host UIDs
+
+## Advanced Usage
+
+### VM Migration Between Workstations
+
+Export your complete VM environment:
+
+```bash
+# Export VM with all data
+clonebox export . --user --include-data -o my-dev-env.tar.gz
+
+# Transfer to new workstation, then import
+clonebox import my-dev-env.tar.gz --user
+clonebox start . --user
+```
+
+### Testing VM Configuration
+
+Validate your VM setup:
+
+```bash
+# Quick test (basic checks)
+clonebox test . --user --quick
+
+# Full test (includes health checks)
+clonebox test . --user --verbose
+```
+
+### Monitoring VM Health
+
+Check VM status from workstation:
+
+```bash
+# Check VM state, IP, cloud-init, and health
+clonebox status . --user
+
+# Trigger health check in VM
+clonebox status . --user --health
+```
+
+### Reopening VM Window
+
+If you close the VM window, you can reopen it:
+
+```bash
+# Open GUI viewer (easiest)
+clonebox open . --user
+
+# Start VM and open GUI (if VM is stopped)
+clonebox start . --user --viewer
+
+# Open GUI for running VM
+virt-viewer --connect qemu:///session clone-clonebox
+
+# List VMs to get the correct name
+clonebox list
+
+# Text console (no GUI)
+virsh --connect qemu:///session console clone-clonebox
+# Press Ctrl + ] to exit console
+```
+
 ## License
 
-MIT License - see [LICENSE](LICENSE) file.
+MIT License - see [LICENSE](LICENSE) file.

{clonebox-0.1.9 → clonebox-0.1.10}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "clonebox"
-version = "0.1.9"
+version = "0.1.10"
 description = "Clone your workstation environment to an isolated VM with selective apps, paths and services"
 readme = "README.md"
 license = {text = "Apache-2.0"}