Commands - Barely docs

The barely command does in the terminal most of what the app does. Where the app has it, the last column says where.

Command	What it does	In the app
`barely status`	Whether the VM is running, and its memory, CPU and disk use	Engine › Status, and the menu bar
`barely top`	A live view of the same, with memory and CPU per container	Containers › Activity
`barely ps`	Every process in the VM, grouped by container	Engine › Processes
`barely shell`	A root shell inside the VM
`barely start`	Start the VM	Start on the Engine screen
`barely stop`	Shut the VM down. This discards a hibernated VM	Stop on the Engine screen
`barely restart`	Restart the VM, which applies config changes	Apply & Restart VM in Settings › Resources
`barely hibernate`	Save the VM to disk now, with its containers as they are	Hibernate on the Engine screen
`barely resume`	Resume a hibernated VM	Resume on the Engine screen
`barely logs`	barely's own logs, add `-follow` to keep watching	Engine › Logs
`barely doctor`	Checks Docker is pointed at barely, and says what to fix if it isn't	Settings › Doctor
`barely licence`	Your trial or licence, see Licence	Settings › Licence
`barely config`	Show, read or change your settings, see Config	Settings › Resources and Settings › Docker
`barely uninstall`	Remove barely, see Uninstall

To see every command and its options:

barely help

For one command, for example status:

barely help status

Questions

No. Your images, containers and volumes stay on disk. Stopping the VM discards a hibernated VM, so the next start boots it fresh.

Most of it. The table's last column says where each command is in the app. A root shell inside the VM and uninstalling are in the terminal only.