The Interactive Dashboard: Managing Servers Without Memorizing Commands

neo with no arguments

Every Neo command has a scriptable form (neo list, neo logs app, neo domain app example.com), but you don't have to remember them. Running neo alone opens an interactive dashboard:

? What would you like to do?
> Servers              2 configured
  Applications         3 apps, 2 running
  Deploy Project        deploy local repo
  Install App           scaffold a template into a folder
  Quit

Arrow keys and Enter navigate; every screen has a way back. Under Applications, selecting an app opens actions for start/stop/restart, viewing logs, changing its domain, updating the image, or removing it.

Log viewing

Selecting View Logs on an app streams its container logs directly in the TUI, following new lines as they arrive — the same output as neo logs <app> -f without leaving the dashboard.

Staying current

neo version and neo upgrade pull real release notes from the same changelog this tutorial site publishes, so neo upgrade tells you what actually changed before you run it — not just a version number.

When to use the dashboard vs. the CLI directly

The dashboard is for exploring and for occasional tasks where you'd otherwise have to look up the exact flag. For anything repeatable — CI, a deploy script, a runbook — use the direct commands; they're what the dashboard calls internally, and they're what you'll want in a script anyway.