Skip to main content
The Terminal tab gives you an interactive shell with keyboard input, scrollback and copy/paste. The VM must be running and reachable by Suji’s management connection.

​
Choose a target

  • Host: opens a shell as root on your VM. Use it to manage system packages, Docker, services and host files.
  • An app install: opens a shell inside a running container for that install, using the container’s configured user. A multi-container install may open one of its running containers; use the host terminal when you need to choose a specific service.
An app terminal uses the tools, working directory and shell provided by the image. Suji does not guarantee that an app-specific CLI is installed or automatically placed in PATH. Follow that app’s current command-line instructions. You can have up to 3 concurrent dashboard terminal connections to a VM.

​
Reconnect to a session

Terminal sessions use tmux on the host. Losing the browser connection or closing its terminal tab can leave the shell and its processes running. Refreshing the same dashboard browser tab can restore its recorded terminal tabs and reconnect to those sessions. This is not durable process hosting: a VM reboot ends its tmux sessions, and restarting or replacing an app container interrupts a shell inside that container. A new browser tab or device may not have the previous session’s tab state. Use a system service or the app’s normal deployment configuration for processes that need to restart automatically. Type exit to leave the current shell. Closing a browser tab alone does not reliably stop work running in the VM. Idle connections may also be disconnected.

​
Useful commands

From the host terminal:
To enter a particular running container, identify its name with docker ps, then use a shell it provides:
Commands run with the permissions of the selected target. Root commands can alter or delete the VM’s data and configuration; inspect a command before running it.

​
Access and transport

The host shell has root authority over your isolated VM. This does not mean the physical server’s CPU hardware is exclusive to you. App shells use the image’s configured user unless you explicitly choose another user through Docker. Terminal transport is encrypted from your browser to Suji and from Suji to the VM. It passes through the platform rather than forming a direct browser-to-VM session.

​
Next

Files

Browse supported directories without shell commands.

Logs

Read system or app output from the dashboard.