tinycloud-init

Set up tinycloud

Walk the user from nothing to a working, verified tinycloud install. End the session with one successful command, not a checklist. Work through the steps in order, skipping any that already pass.

1. Is the CLI installed?

command -v tinycloud && tinycloud --version --json </dev/null

If installed and the JSON reports "version" ≥ 0.3.0, go to step 2. If missing (or no machine-readable version), install it — ask the user which they prefer:

npm install -g @cloudglue/tinycloud          # canonical (Node >= 18)
# or
curl -fsSL https://app.cloudglue.dev/tinycloud.sh | bash

The first run downloads the platform distribution (~90 MB, one time). More at https://tinycloud.sh. Windows is unsupported — use WSL2.

2. Is a Cloudglue API key configured?

tinycloud setup --check --json </dev/null

If data.ok is true, go to step 3. Otherwise tell the user: cloud features run through a Cloudglue account — keys live at app.cloudglue.dev (usage billed per the rate card). Ask them to paste their API key, then configure it via stdin so the key never lands in shell history or process args:

printf '%s' "<key>" | tinycloud setup cloudglue --stdin

Re-run tinycloud setup --check --json and confirm data.ok == true.

3. Prove it works (free)

tinycloud workflow validate summary --json    # exercises the recipe engine, no cloud calls

Expect status: "ready". If the user provided a video ($video) or has one handy, also show them something real — still free and local:

tinycloud clip info <video> --json            # duration/resolution/codecs via bundled ffprobe

4. Hand off

Report what's now working and point forward:

• "Analyze a video": tinycloud watch <video> --json (first cloud call — uses the API key)
• One-command workflows: tinycloud workflow list --json (sales-coaching, blog-post, ad-analysis, meeting-breakdown, youtube-publish, …)
• If the general tinycloud skill is installed alongside this one, it documents the full CLI, envelope contract, and a glossary; its scripts/preflight.sh re-checks this setup any time.

Troubleshooting

• tinycloud found but --version --json prints a UI instead of JSON → pre-0.3.0 install; upgrade via either install command above.
• setup --check reports ok: false after configuring → key was rejected; re-paste it (watch for stray whitespace) or generate a fresh key.
• Corporate proxy: the npm launcher honors HTTPS_PROXY (falls back to curl for the download).