Easy Setup — No Package Manager, No Account, No Cloud

Single Python file. Python 3.8+ standard library only — nothing to pip install. Run with:

python wps-recipe.py

Sample plan files ship with the download and run out of the box. Pair with WonderPhi Compute to execute the generated plans in parallel.

WonderPhi Server — 19 batch recipes for VM & server administration

Nineteen recipes for the operations you run on every server in your fleet: Hyper-V and WSL lifecycle, SSH command fan-out, WinRM control, snapshot / restart / update patterns. Point at a host list, get a plan file. Every host, every operation, in parallel.

What it is, in plain English

Give a recipe a list of hostnames (one per line in a text file). It emits a plan file — one command per host. WonderPhi Compute runs every command in parallel. When it's done, you have a per-host log of what happened. If host #37 failed, you know exactly which one and why.

How you use it — three steps

1. Run the recipe file. python wps-recipe.py in the folder that contains your input files, or wherever you want the plan written.
2. Point at the target. The recipe asks (or reads from a text file) what the input is — a folder, a list of hostnames, a CSV, whatever the recipe expects. It writes a plan file: one shell command per line.
3. Hand the plan to Compute. Drop the generated plan.wpc.txt into the WonderPhi Compute inbox, and every command runs in parallel across your cores. Read the honest log when it's done.

Worked examples — three of the 19 recipes in this library

ssh-fanout — run one command on every host in a list

Point at a hostnames.txt. Recipe emits an SSH plan-line per host. All 500 hosts execute at once.

python wps-recipe.py ssh-fanout --hosts hosts.txt --cmd 'sudo systemctl restart nginx'

# generated:
# ssh admin@web01.example.com 'sudo systemctl restart nginx' >> web01.log
# ssh admin@web02.example.com 'sudo systemctl restart nginx' >> web02.log
# ... (one line per host)

hyperv-snapshot-all — snapshot every running VM before a maintenance window

Reads Hyper-V, generates a plan that snapshots each VM by name.

python wps-recipe.py hyperv-snapshot-all --tag pre-maintenance-2026-07-23

wsl-distro-update — update all WSL distros in parallel

One plan-line per distro. All updates run at once (isolated distros, no shared state).

python wps-recipe.py wsl-distro-update

Under the hood — the honest technical picture

Every recipe emits shell-command plan-lines that use the standard tools already on your Windows workstation: ssh (via OpenSSH-for-Windows or WSL), Enter-PSSession / Invoke-Command (WinRM), Get-VM / Start-VM (Hyper-V module), and wsl. Nothing is installed on the remote hosts; nothing is installed locally beyond what Windows already ships.

• No agent on remote hosts. Uses existing SSH / WinRM.
• Read-only unless you tell it otherwise. Recipes that snapshot or restart make it obvious in the recipe name.
• Host list format is trivial: one hostname per line, blank lines and # comments allowed.
• Recipes emit the exact command they'd run. You can hand-verify one line before letting Compute run all 500.
• Logs land per-host. The plan-line for host web37 writes its stdout/stderr to logs/web37.log.

How it compares to the manual way

What you need

• Windows 10 / 11 as the operator's machine (recipes use PowerShell/OpenSSH from Windows).
• Whichever remote-access tool your fleet uses: OpenSSH, WinRM, or the Hyper-V module. Recipes don't install these — they use what's already there.
• Python 3.8+ to generate the plan file. Standard library only.
• WonderPhi Compute to run the generated plan in parallel across cores.

What's in the download

• wps-recipe.py — the recipe generator (Python 3.8+, standard library only)
• README.md — per-recipe reference for humans
• INDEX.md — alphabetical list of every recipe with a one-line description
• samples/ — ready-to-run demo input files for every recipe
• LICENSE.txt — perpetual single-user license, personalized with your name and order number at delivery

Common questions

License & support

Retail single-user license, perpetual, non-transferable. Every download's LICENSE.txt is personalized at checkout with your name, email, and order number. Full terms live inside your download — short version: install on any machine you personally own and operate, don't redistribute, don't run it as a paid service for third parties (that needs the Industrial variant), and everything else is fine.

Support: email chris@cri-one.com. Because WonderPhi Server — 19 batch recipes for VM & server administration never changes, there's nothing to "support" in the update sense — but if something isn't behaving the way you expect, write and I'll help.

USA-only sales for retail.