sarman/dgx-spark-playbooks
1
0
Fork 0
mirror of https://github.com/NVIDIA/dgx-spark-playbooks.git synced 2026-04-23 18:33:54 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
34cd09b53e
dgx-spark-playbooks/overrides/connect-to-your-spark.md
Jason Kneen a680d0472b feat: scaffold skills plugin from DGX Spark playbooks 
Adds a Claude Code plugin structure that exposes each NVIDIA DGX Spark
playbook as a triggerable skill, with an index skill ('dgx-spark') that
routes users to the right leaf based on intent and encodes the
relationship graph between playbooks (prerequisites, alternatives,
composes-with, upgrade paths).

Structure:
- overrides/*.md       hand-curated frontmatter + Related sections
- scripts/generate.mjs zero-dep Node generator: nvidia + overrides → skills
- scripts/install.sh   symlinks skills into ~/.claude/skills (--plugin mode available)
- skills/              committed, browsable, installable without Node
- .github/workflows/   auto-regenerates skills/ when playbooks/overrides change

Initial curated leaves: ollama, open-webui, vllm, connect-to-your-spark.
Remaining 37 leaves use generator fallback (title + tagline + summary
extracted from README) and can be curated incrementally via overrides/.
2026-04-19 10:22:08 +01:00

2.5 KiB
Raw Blame History

description
Set up SSH access to an NVIDIA DGX Spark from a laptop using NVIDIA Sync (recommended) or manual SSH. Use when a user is new to their Spark and needs to connect remotely, before doing anything else. This is a prerequisite for nearly every other dgx-spark-* skill — if a user hasn't set this up, do this first.

When to use this skill

  • User just got their DGX Spark and wants to use it from their laptop
  • Any other dgx-spark-* skill needs SSH access and the user hasn't configured it yet
  • User reports "can't connect to my Spark" or "SSH hangs / can't resolve spark-abcd.local"

Two paths — help the user pick

  • NVIDIA Sync (recommended) — GUI, handles SSH key generation + aliasing + port forwarding for apps. Required if they want one-click app launchers (DGX Dashboard, VS Code, Open WebUI tunnels).
  • Manual SSH — if they prefer CLI-only workflow, or Sync isn't supported on their platform.

Most users should use NVIDIA Sync unless they have a specific reason not to.

Key decisions

  • Hostname vs IP — default is mDNS hostname (spark-abcd.local). On corporate networks that block mDNS, they'll need to use the IP address from their router's admin panel. Quick test: ping spark-abcd.local — if it hangs, mDNS is blocked.
  • First-boot wait — after initial system setup, the Spark can take 3–4 minutes to finish updates before SSH becomes available. Don't diagnose connection issues in this window.

Non-obvious gotchas

  • NVIDIA Sync's password prompt happens once — it uses the password only to install the SSH key, then discards it. If auth fails, the key install didn't complete; re-run the add-device flow.
  • mDNS .local resolution is OS + network-stack specific. Works on most home Wi-Fi; often broken on corporate VPNs or guest networks.
  • Port-forwarding for web apps is a separate step (SSH -L flag or Custom Ports in Sync) — connecting to SSH alone doesn't give laptop browsers access to web UIs running on the Spark.

Related skills

  • Alternative: dgx-spark-tailscale — use Tailscale VPN for remote access instead of local-network SSH. Works off-network.
  • Follow-ups (what users typically do next):
    • dgx-spark-ollama — run a local LLM
    • dgx-spark-open-webui — web chat UI
    • dgx-spark-vscode — remote development
    • dgx-spark-dgx-dashboard — system monitoring (already pre-installed, just needs the tunnel)
  • Multi-Spark setups depend on this first: dgx-spark-connect-two-sparks, dgx-spark-connect-three-sparks, dgx-spark-multi-sparks-through-switch