pvectl 0.2.0

data/CLAUDE.md

@@ -0,0 +1,211 @@
+# CLAUDE.md
+
+Guidelines for Claude Code when working with this repository.
+
+## Project Overview
+
+**pvectl** is a Ruby CLI gem for managing Proxmox clusters with kubectl-like syntax. It wraps the Proxmox API, exposing familiar commands for VM/container management, node operations, storage, backups, and snapshots.
+
+## Developer Commands
+
+```bash
+bin/setup              # Install dependencies
+rake test              # Run tests (prefer /test-run)
+bin/console            # Interactive console
+bundle exec exe/pvectl # Run CLI locally
+bundle exec rake release # Release new version
+```
+
+**Ruby:** 3.3.0 (`.ruby-version`)
+
+## Architecture
+
+### Layer Diagram
+
+Two data paths depending on operation type:
+
+```
+                    ┌──────────────────────────────────┐
+                    │           CLI Layer               │
+                    │  GLI::App (cli.rb) → PluginLoader │
+                    │  → Commands (.register)           │
+                    └────────┬─────────────┬───────────┘
+                             │             │
+                  read-only  │             │  mutating
+              (get,top,logs, │             │  (lifecycle,delete,
+               describe)     │             │   clone,create,edit,
+                             ▼             ▼   migrate)
+                    ┌──────────┐  ┌─────────────────┐
+                    │ Handlers │  │    Services      │
+                    │ +Registry│  │  (orchestration) │
+                    └────┬─────┘  └───────┬─────────┘
+                         │                │
+                         └───────┬────────┘
+                                 ▼
+                    ┌──────────────────────┐
+                    │    Repositories      │
+                    │  → Models → Parsers  │
+                    │  → Connection        │
+                    └──────────┬───────────┘
+                               ▼
+                         Proxmox API
+
+        Presentation (both paths):
+        Models → Presenters → Formatters → Output
+```
+
+### Module Layers (`lib/pvectl/`)
+
+| Directory | Role |
+|-----------|------|
+| `commands/` | Self-registering command classes (`.register(cli)`), Template Method hierarchies, SharedFlags |
+| `commands/*/handlers/` | Per-resource handlers for read-only commands (dispatched via Registry) |
+| `services/` | Orchestration of complex operations (lifecycle, CRUD, migration, resource fetching) |
+| `repositories/` | Proxmox API encapsulation, conversion to domain models |
+| `models/` | Domain models (value objects) |
+| `presenters/` | Column definitions and formatting per resource type |
+| `formatters/` | Output strategies (table, json, yaml, wide) |
+| `parsers/` | Proxmox config parsers (net, disk, cloud-init, LXC mount) |
+| `selectors/` | Resource filtering by attributes (`-l status=running,tags=prod`) |
+| `wizards/` | Interactive resource creators (step-by-step prompts) |
+| `utils/` | Helper utilities (resource resolver) |
+| `config/` | Loading, validation, saving multi-context configuration |
+| `connection/` | API client with retry (exp. backoff) and timeout |
+| `console/` | Interactive terminal session (WebSocket I/O, xtermjs protocol) |
+| `plugin_loader.rb` | Command discovery and loading (built-in + gem/directory plugins) |
+
+### Design Patterns
+
+| Pattern | Usage |
+|---------|-------|
+| **Repository** | API encapsulation, conversion to domain models |
+| **Presenter** | Column definitions and formatting per resource type |
+| **Strategy** | Formatters (Table, JSON, YAML, Wide) |
+| **Registry** | Base registry mapping resource name → handler; each read-only command inherits its own copy |
+| **Handler** | Per-resource handlers in read-only commands, dispatched via Registry |
+| **Template Method** | Base module defines flow, specializations (VM/Container) implement hooks — used in lifecycle, delete, create, edit, migrate |
+| **Dependency Injection** | Repositories and services injected via constructor (testable with mocks) |
+| **Self-Registration** | Each command class implements `.register(cli)` to define its flags/desc/action with GLI |
+| **Plugin Discovery** | `PluginLoader` discovers commands from built-ins, gem plugins (`pvectl-plugin-*`), and directory plugins (`~/.pvectl/plugins/`) |
+
+### Hybrid Module Include Pattern
+
+Pattern used in Template Method specializations (VM/Container) for correct MRO with ClassMethods propagation:
+
+```ruby
+module VmSpecialization
+  include BaseTemplate  # MRO: Specialization BEFORE Base in ancestors
+
+  def self.included(base)
+    base.extend(BaseTemplate::ClassMethods)  # propagate class methods
+  end
+end
+```
+
+**Note:** `self.included(base) { base.include(Base...) }` is **incorrect** — it places Base BEFORE Specialization in MRO, so template methods (NotImplementedError) mask implementations.
+
+### Typed OperationResult Pattern
+
+Mutating operations return a typed `OperationResult` with a subclass per resource type. Each type has a dedicated Presenter with resource-specific columns (e.g., VMID vs CTID). New resource type = new subclass + presenter.
+
+## Configuration
+
+### Config File Format (`~/.pvectl/config`)
+
+```yaml
+apiVersion: pvectl/v1
+kind: Config
+
+clusters:
+  - name: production
+    cluster:
+      server: https://pve1.example.com:8006
+      insecure-skip-tls-verify: false
+
+users:
+  - name: admin-prod
+    user:
+      token-id: root@pam!pvectl
+      token-secret: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
+
+contexts:
+  - name: prod
+    context:
+      cluster: production
+      user: admin-prod
+      default-node: pve1
+
+current-context: prod
+```
+
+### Environment Variables (higher priority than config file)
+
+| Variable | Description |
+|----------|-------------|
+| `PROXMOX_HOST` | Server URL |
+| `PROXMOX_TOKEN_ID` | API token ID |
+| `PROXMOX_TOKEN_SECRET` | Token secret |
+| `PROXMOX_USER` / `PROXMOX_PASSWORD` | Alternative to token |
+| `PROXMOX_VERIFY_SSL` | SSL verification |
+| `PROXMOX_TIMEOUT` | Timeout (seconds) |
+| `PVECTL_CONTEXT` | Context override |
+| `PVECTL_CONFIG` | Alternative config path |
+
+### Loading Hierarchy
+
+```
+Built-in defaults → Config file → ENV variables → CLI flags
+```
+
+## Conventions
+
+### CLI (kubectl style)
+
+Commands grouped by type:
+
+| Group | Commands | Pattern |
+|-------|----------|---------|
+| **Read-only** | `get`, `describe`, `top`, `logs` | Handler + Registry |
+| **Lifecycle** | `start`, `stop`, `shutdown`, `restart`, `reset`, `suspend`, `resume` | Template Method (VM/Container) |
+| **CRUD (VM/CT)** | `create`, `delete`, `edit`, `migrate` | Template Method (VM/Container) |
+| **Snapshot/Backup** | `create`/`delete` snapshot/backup, `rollback`, `restore` | Dedicated commands |
+| **Standalone** | `clone`, `ping` | Dedicated commands per resource type |
+| **Config** | `config <subcommand>` | Self-registration (`register_subcommand`) |
+
+Syntax: `pvectl <command> <resource_type> [id...] [--flags]`
+
+### Exit Codes
+
+| Code | Meaning |
+|------|---------|
+| 0 | Success |
+| 1 | General error |
+| 2 | CLI usage error |
+| 3 | Configuration error |
+| 4 | API connection error |
+| 5 | Resource not found |
+| 6 | Permission denied |
+| 130 | Interrupted (Ctrl+C) |
+
+### Testing
+
+Use `/test-run` instead of `rake test` directly — provides intelligent error analysis.
+
+**Structure:** `test/unit/` mirrors `lib/pvectl/`, convention: `<class>_test.rb`
+
+### Ruby Code Style
+
+Follow the [Ruby Style Guide](https://rubystyle.guide). Write **idiomatic Ruby** — leverage the language's unique features (blocks, iterators, `attr_*`, `?`/`!`/`=` suffixes), don't translate patterns from other languages.
+
+### Code Documentation (RDoc)
+
+Required for classes, modules, and public methods:
+- `@param`, `@return`, `@raise`, `@example`
+
+## MCP Servers
+
+| Server | Libraries (libraryId) |
+|--------|------------------------|
+| `context7` | `/davetron5000/gli`, `/piotrmurach/tty-table`, `/minitest/minitest`, `/L-Eugene/proxmox-api` |
+
+**Configuration:** `.mcp.json`

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[INSERT CONTACT METHOD].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2025 Piotr Wojcieszonek
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,143 @@
+# pvectl
+
+A command-line tool for managing Proxmox clusters with kubectl-like syntax.
+
+**pvectl** wraps the Proxmox API as a Ruby gem, providing familiar commands for managing VMs, containers, nodes, storage, backups, and snapshots from the terminal.
+
+> **Note:** This project is in active development. Some features may not yet be fully stable.
+
+## Features
+
+- **kubectl-like syntax** — familiar commands: `get`, `describe`, `top`, `logs`
+- **Multi-resource management** — VMs, containers, nodes, storage, snapshots, backups
+- **Batch operations** — act on multiple resources with selectors: `-l status=running`
+- **Multiple output formats** — table, wide, JSON, YAML
+- **Watch mode** — auto-refreshing resource lists
+- **Interactive wizards** — guided VM/container creation
+- **Console access** — interactive terminal sessions via WebSocket
+- **Multi-cluster contexts** — kubeconfig-style context switching
+- **Plugin system** — extend with gem-based or directory-based plugins
+- **Template management** — convert VMs/containers to templates, linked cloning
+
+## Installation
+
+```bash
+gem install pvectl
+```
+
+Or add to your Gemfile:
+
+```bash
+bundle add pvectl
+```
+
+**Requirements:** Ruby >= 3.0.0
+
+## Quick Start
+
+On first run, pvectl launches an interactive configuration wizard:
+
+```bash
+$ pvectl get nodes
+Proxmox server URL (e.g., https://pve.example.com:8006): https://pve.example.com:8006
+Verify SSL certificate? (y/n) y
+Authentication method:
+  1. API Token (recommended)
+  2. Username/Password
+Enter number: 1
+Token ID (e.g., root@pam!tokenid): root@pam!pvectl
+Token Secret: ********
+Context name: [default] production
+```
+
+Once configured, explore your cluster:
+
+```bash
+pvectl get nodes                  # List cluster nodes
+pvectl get vms                    # List all VMs
+pvectl get vms -o wide            # Extended columns
+pvectl get subscription           # Show Proxmox subscription per node (key masked)
+pvectl describe vm 100            # Detailed VM info
+pvectl top nodes                  # Resource usage
+```
+
+## Commands
+
+| Command | Description |
+|---------|-------------|
+| `get` | List resources (nodes, VMs, containers, storage, disks, volumes, snapshots, backups, tasks, dns, services, hosts, node-capabilities, subscription) |
+| `describe` | Show detailed information about a resource (nodes, VMs, containers, storage, disks, volumes, snapshots) |
+| `top` | Display resource usage metrics (CPU, memory, disk) |
+| `logs` | Show logs and task history (syslog, journal, task detail) |
+| `start` `stop` `shutdown` `restart` | Lifecycle management |
+| `create` | Create VMs, containers, snapshots, or backups |
+| `delete` | Delete resources |
+| `clone` | Clone VMs or containers with optional config changes |
+| `migrate` | Migrate resources between nodes (supports live migration) |
+| `move disk` | Move VM disk / container volume between storages on the same node |
+| `feature` | Query whether a feature (clone/snapshot/copy) is available for a VM/CT |
+| `edit` | Edit resource configuration in $EDITOR (vm, container, node, volume, dns, hosts) |
+| `set` | Set resource properties non-interactively with key=value pairs |
+| `pull` | Export resource configuration as kubectl-like YAML manifests |
+| `push` | Apply YAML manifests to cluster (create or update resources) |
+| `template` | Convert VM/container to template |
+| `unlink` | Unlink disk(s) from a VM (keep volume as `unused[n]` or delete with `--force`) |
+| `rollback` | Rollback to a snapshot |
+| `restore` | Restore from a backup |
+| `console` | Interactive terminal session |
+| `service` | Manage systemd services on Proxmox nodes (start, stop, restart, reload) |
+| `apt` | Manage APT packages on Proxmox nodes (list, update, changelog, versions) |
+| `cloudinit` | Manage cloud-init for VMs (`regenerate`, `pending`, `dump`) |
+| `sendkey` | Send a QEMU monitor key event to a VM (e.g., `ctrl-alt-delete`) |
+| `ping` | Check cluster connectivity |
+| `wakeonlan` | Send Wake-on-LAN packet to a cluster node |
+| `config` | Manage configuration (contexts, clusters, credentials) |
+
+Use `pvectl help <command>` for detailed usage, examples, and options.
+
+## Documentation
+
+Full documentation is available in the [GitHub Wiki](https://github.com/pwojcieszonek/pvectl/wiki):
+
+- **[Getting Started](https://github.com/pwojcieszonek/pvectl/wiki/Getting-Started)** — installation, configuration, first commands
+- **[Configuration Guide](https://github.com/pwojcieszonek/pvectl/wiki/Configuration-Guide)** — contexts, auth methods, environment variables
+- **[Command Reference](https://github.com/pwojcieszonek/pvectl/wiki/Command-Reference)** — detailed docs for every command
+- **[Selectors & Filtering](https://github.com/pwojcieszonek/pvectl/wiki/Selectors-and-Filtering)** — filter resources with `-l` flag
+- **[Output Formats](https://github.com/pwojcieszonek/pvectl/wiki/Output-Formats)** — table, wide, JSON, YAML
+- **[Workflows](https://github.com/pwojcieszonek/pvectl/wiki/Workflows)** — common scenarios and best practices
+- **[Plugin Development](https://github.com/pwojcieszonek/pvectl/wiki/Plugin-Development)** — extend pvectl with custom commands
+- **[Troubleshooting](https://github.com/pwojcieszonek/pvectl/wiki/Troubleshooting)** — common issues and solutions
+
+## Configuration
+
+Configuration file: `~/.pvectl/config` (kubeconfig-style YAML)
+
+```bash
+pvectl config view                      # Show current config
+pvectl config get-contexts              # List contexts
+pvectl config use-context production    # Switch context
+```
+
+See the [Configuration Guide](https://github.com/pwojcieszonek/pvectl/wiki/Configuration-Guide) for details on multi-cluster setup, authentication methods, and environment variables.
+
+## Plugins
+
+pvectl supports plugins via gems (`pvectl-plugin-*`) and local files (`~/.pvectl/plugins/*.rb`). See [Plugin Development](https://github.com/pwojcieszonek/pvectl/wiki/Plugin-Development).
+
+## Development
+
+```bash
+git clone https://github.com/pwojcieszonek/pvectl.git
+cd pvectl
+bin/setup
+rake test
+bundle exec exe/pvectl
+```
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at [https://github.com/pwojcieszonek/pvectl](https://github.com/pwojcieszonek/pvectl).
+
+## License
+
+Released under the [MIT License](https://opensource.org/licenses/MIT).

data/Rakefile

@@ -0,0 +1,8 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "minitest/test_task"
+
+Minitest::TestTask.create
+
+task default: :test

data/docs/proxmox-api-update.sh

@@ -0,0 +1,96 @@
+#!/usr/bin/env bash
+# Downloads and parses Proxmox VE API documentation into per-section JSON files.
+# Output: docs/proxmox-api/*.json
+#
+# Usage: bash docs/proxmox-api-update.sh
+
+set -euo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
+PROJECT_DIR="$(dirname "$SCRIPT_DIR")"
+OUTDIR="$PROJECT_DIR/docs/proxmox-api"
+TMPFILE="$(mktemp)"
+URL="https://raw.githubusercontent.com/proxmox/pve-docs/master/api-viewer/apidata.js"
+
+echo "Downloading apidata.js..."
+curl -sL "$URL" -o "$TMPFILE"
+
+echo "Parsing and splitting into per-section JSON files..."
+mkdir -p "$OUTDIR"
+rm -f "$OUTDIR"/*.json
+
+ruby -e '
+require "json"
+
+raw = File.read(ARGV[0])
+json_str = raw.sub(/\Aconst apiSchema = /, "").sub(/;\s*\z/, "")
+data = JSON.parse(json_str)
+outdir = ARGV[1]
+
+def flatten_endpoints(node, result = [])
+  info = node.dup
+  children = info.delete("children")
+  result << info unless info["path"].nil?
+  (children || []).each { |child| flatten_endpoints(child, result) }
+  result
+end
+
+def split_by_subpath(entries, depth)
+  groups = {}
+  entries.each do |ep|
+    parts = ep["path"].split("/")
+    key = parts[depth] || "root"
+    groups[key] ||= []
+    groups[key] << ep
+  end
+  groups
+end
+
+data.each do |top|
+  path = top["path"].sub("/", "")
+
+  if path == "nodes"
+    # Split /nodes by resource type (qemu, lxc, storage, etc.)
+    (top["children"] || []).each do |node_child|
+      (node_child["children"] || []).each do |resource|
+        key = resource["path"].split("/")[3] || "root"
+        endpoints = flatten_endpoints(resource)
+
+        # Further split large sections (qemu, lxc, cluster) by sub-resource
+        if endpoints.size > 20
+          sub_groups = split_by_subpath(endpoints, 5)
+          sub_groups.each do |sub_key, sub_eps|
+            outfile = File.join(outdir, "nodes-#{key}-#{sub_key}.json")
+            File.write(outfile, JSON.pretty_generate(sub_eps))
+          end
+        else
+          outfile = File.join(outdir, "nodes-#{key}.json")
+          File.write(outfile, JSON.pretty_generate(endpoints))
+        end
+      end
+      # Root node info
+      info = node_child.dup
+      info.delete("children")
+      File.write(File.join(outdir, "nodes-root.json"), JSON.pretty_generate([info]))
+    end
+  elsif path == "cluster"
+    # Split /cluster by sub-section
+    endpoints = flatten_endpoints(top)
+    sub_groups = split_by_subpath(endpoints, 2)
+    sub_groups.each do |key, eps|
+      outfile = File.join(outdir, "cluster-#{key}.json")
+      File.write(outfile, JSON.pretty_generate(eps))
+    end
+  else
+    endpoints = flatten_endpoints(top)
+    outfile = File.join(outdir, "#{path}.json")
+    File.write(outfile, JSON.pretty_generate(endpoints))
+  end
+end
+' "$TMPFILE" "$OUTDIR"
+
+rm -f "$TMPFILE"
+
+count=$(ls -1 "$OUTDIR"/*.json 2>/dev/null | wc -l | tr -d ' ')
+total_size=$(du -sh "$OUTDIR" | cut -f1)
+echo "Done: $count files, $total_size total in $OUTDIR"

data/exe/pvectl

@@ -0,0 +1,5 @@
+#!/usr/bin/env ruby
+
+require "pvectl"
+
+exit Pvectl::CLI.run(Pvectl::ArgvPreprocessor.process(ARGV))