jumpgate
  1. Docs
  2. The TUI
  3. Keys

Keys

The keys that work on every screen.

How you got here: Desktop app Terminal only: TUI and CLI One server for everything Screens

Show previous steps 4
Install 2
  1. Desktop app

    Download the desktop app for your OS and open it.

    The macOS zip holds Jumpgate.app and Jumpgate Terminal.app; Windows has jumpgate-tray.exe and jumpgate.exe; Linux has install.sh. Every download carries both Linux agents.

    Show image
    The app panel's Home tab: the gateway running two networks.
    Illustration from the jumpgate.app demo, with made-up boxes; not a screenshot of the app.
  2. Terminal only: TUI and CLI

    The jumpgate binary alone, for servers and scripts.

    The jumpgate_<os>_<arch> archives hold one binary with the TUI, the CLI and the server. Run jumpgate in a terminal to open the TUI.

    Show image
    The Fleet screen: every box with its link, network, sync, lag, peers, disk and firewall.
    The TUI, from its test snapshot; empty rows removed.
Getting started 1
  1. One server for everything

    The app, TUI and CLI share one background server.

    Whichever starts first runs the server; quitting the TUI leaves it running and jumpgate stop ends it.

The TUI 1
  1. Screens

    The six screens: Fleet, Hosts, Signers, Gateways, Jobs, Settings.

    1 to 6 switch screens; Enter on a box opens its tabs, from Overview to Services.

    Show image
    The Fleet screen: every box with its link, network, sync, lag, peers, disk and firewall.
    The TUI, from its test snapshot; empty rows removed.
The help screen: the keys that work everywhere, then the keys for the current screen.
The TUI, from its test snapshot; empty rows removed.

Stopping or restarting a service asks you to type its name.