:try · a real Nutsh on two invented Prism Centrals · nothing real behind it

See it before you trust it a password.

Click in, press ?. It is yours alone, and nothing you do reaches anything real.

try.nutsh.dev · one sandboxed session · keyboard in, screen outopen full screen ↗

Click inside, then ? for the keys, : for the prompt, :vm for the VM table, a on a row for its actions. A phone works but wants a keyboard.

What this is. A mock: two invented Prism Centrals, invented clusters, invented VMs, served by the same mock the test suite runs against. Nothing here is anyone's infrastructure. Sessions are recorded as screen output to fix bugs and deleted after fourteen days; keystrokes are never stored.

:install

Two lines, one of them yours.

macOS and Linux, x86_64 and ARM64. The Linux archives come as gnu and musl, the second a static binary for any distribution. Every archive ships with its SHA-256; releases from 0.2.0 carry a GitHub build attestation. Windows is WSL2 for now.

homebrew · macOS and Linux$ brew install Fen0l/tap/nutsh

shell · any distribution$ curl -LsSf https://github.com/Fen0l/nutsh/releases/latest/download/nutsh-installer.sh | sh

Then nutsh ctx add lab --host your-prism-central --username you, nutsh ctx login lab, and nutsh. Add --readonly to the first command if the Prism Central matters.

:comments

Say what you found.

What looked wrong, what you expected, which Prism Central version you would run it against. Comments are GitHub Discussions on the repository, so a GitHub account is the only thing needed. Bugs with steps go to the issue templates; everything else fits here.

Comments open here shortly. Until then, the discussions on GitHub are the same thread.