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 wph-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 Host — 24 batch recipes for website hosting operations

Twenty-four recipes for the daily ops of running websites: nginx test/reload, TLS certificate lifecycle, backup + rsync, log operations, deploys, HTTP audits, DNS checks, SEO pings. Point at a domain list, get a parallel plan.

What it is, in plain English

Give a recipe a list of domains (one per line). It emits a plan — one shell command per domain, using the tool for the job (certbot, openssl, curl, nslookup, rsync). Compute runs everything in parallel. You get per-domain results in a log file, filed by hostname.

How you use it — three steps

1. Run the recipe file. python wph-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 24 recipes in this library

http-status-all — every domain, HEAD check + status code

In under a minute you know which of your 300 sites are up, redirecting, throwing 500s, or timing out.

python wph-recipe.py http-status --domains sites.txt --output status.tsv

# emitted plan:
# curl -sI -o /dev/null -w '%{http_code}\t%{time_total}\n' https://alpha.example.com >> status.tsv
# curl -sI -o /dev/null -w '%{http_code}\t%{time_total}\n' https://beta.example.com >> status.tsv

tls-days-until-expiry — audit certs across your fleet

Recipe hits each domain's :443, parses the cert, prints days-until-expiry. Sort output and see everything expiring in the next 30 days.

python wph-recipe.py tls-days --domains domains.txt --output tls-audit.tsv

nginx-reload-fleet — safely reload nginx across every web node

Each plan-line does test-config first, then reload. If test-config fails, the reload is skipped for that host.

python wph-recipe.py nginx-reload --hosts web-nodes.txt

Under the hood — the honest technical picture

Every recipe emits shell commands that call the standard operator tools: curl, openssl, nslookup, rsync, certbot, tar, mysqldump, nginx, apachectl. The recipe never re-implements these; it delegates. That means every command it emits is one you already trust.

• Uses standard operator tools. Nothing to install on the workstation beyond what a sysadmin already has.
• Read-only where possible. Audit recipes never change server state. Destructive recipes (reload, deploy) name themselves.
• Per-domain isolation. A DNS lookup failure for one domain doesn't stop the other 499.
• Recipes emit deterministic output — TSV / CSV files that pipe cleanly into whatever monitoring or reporting you already use.
• No agent on your web servers. Everything runs over SSH or is a local curl from your workstation.

How it compares to the manual way

What you need

• Windows / macOS / Linux as the operator's workstation.
• The tools each recipe wraps: openssh, curl, openssl, rsync, nslookup. All standard on Linux/macOS; on Windows they ship with recent 10/11.
• Python 3.8+ to generate the plan. Standard library only.
• WonderPhi Compute to run the plan in parallel.

What's in the download

• wph-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 Host — 24 batch recipes for website hosting operations 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.