The command centre

seawall tui is the same commands in a live screen.

Tabs and keys

seawall tui

The command centre has eight tabs. It reloads when Docker's events say a container changed, and every 30 seconds otherwise. A change runs as a dry run in a pane where its command has one. y confirms it and the prompt names the change. A failed dry run is never offered.

TabKeys
1 Overviewenter open the row's tab · f the row's fix · F fix all · C copy its check · S silence · d f K a rule file's diff, take seawall's, keep yours
2 Hosto clean up · v volumes · m memory by stack · [ ] graph window
3 Stacksenter details · n new · l logs · D deploy · u update · s stop or start · h harden · v env · W games folder · more from the space menu
4 Alertsenter the alert in full · f its action · C copy its check · S silence · x end a silence
5 Securityenter details · f the row's fix · U rescan
6 Backupsb back up · t restore test · R restore · N nightly dumps · S back up data
7 Logenter the change · u undo it where seawall can · / find · v levels
8 Networkenter details · f the row's fix · l lint · R rename a network · B bans · n networks
Everywhere1-8 or ← → tabs · ↑ ↓ select · space every action · r refresh · ? help · a about · q quit

q or esc closes the logs pane. A change keeps running when you press esc. Ctrl+C stops it.

The logs pane with error lines in red and warning lines in yellow
Followed logs with errors and warnings coloured.

Light terminals and the mouse

seawall draws for a dark background unless the terminal's COLORFGBG says it's light. On a light terminal that doesn't say so, set Background to light in settings (,, Command centre), or with:

seawall config set tui.ground light --yes

The command centre and the CLI then draw in darker shades. dark or light outranks the terminal, and auto reads it again.

A click picks a row or a tab and the wheel scrolls. Shift and a drag select text in most terminals. With tui.mouse off the mouse is the terminal's, and a drag selects text:

seawall config set tui.mouse off --yes

Overview

The Overview opens on one line of the host's vitals with CPU, memory, the root disk and the days until it fills, uptime and the last backup. To do comes next, one line a row with what it is, where and the key that fixes it. To look at holds what seawall can't fix, the alerts of one rule as one row, and Enter opens a row in its tab. Areas sums up stacks, exposure, updates, backups and the config repo. The last change sits at the bottom. On a phone-sized terminal the vitals stay one line and the area lines drop.

Changes in the background

A change's plan opens as a popover over the screen, its confirm in it: Enter, or the name typed for a change that's hard to undo. Any other key closes it and nothing runs. Confirmed, the change runs as a job, and the command centre stays where you were. The Jobs tray at the foot of every tab holds a line for each job, with its step while it runs and then how it ended. J moves into the tray and Enter opens a job's steps. u on a job that ended well opens its undo's plan for an update, a deploy, limits, harden, grafana rules adopt or notify link. On Stacks, a stack's State column shows its job's step, and w or the first line of its menu opens the job. Jobs carry on after the command centre quits, and the next one shows them.

Four jobs run at once. A fifth waits in the tray as queued and starts when one ends, unless the command centre quits first. A stack takes one change at a time, and a host change runs alone. The same rules hold for changes from another terminal and from the nightly timers. A trial waits for the one before it to end and shows the memory free and the floor its copy has to leave.

Security and Alerts

The Security tab puts each section's findings first with a count in its title, and folds a section where every row passes. Patching shows images with Critical or High fixes, CVEs, host updates, Docker and the CrowdSec bouncer. A row with a fix offers f.

An alert's detail shows what was found, the action f takes and the check to run. The first action is always the fix. Log lines in an alert or a stack's logs are shown with the stack's env values masked.

The Network tab

The Network tab is how traffic gets in. Its first line names the way in with the proxy, its network, its ports, the CrowdSec bouncer and the firewall. Sites lists each domain the proxy routes with its backend. Published lists each port the host publishes against the allowlist, and f allows one that isn't expected. Networks lists each Docker network with its subnet, owner and the stacks on it. l lints a network's keys and R renames it. On a phone-sized terminal the networks sit behind n.

The Network tab with the way in, sites, networks and published ports
The Network tab.

The Stacks tab

Each row shows who runs the stack, its state, any update and how hardened it is. The Safety column reads ✓ when nothing is missing, ! and the gap (caps, socket, admin port, no limits) when something is, ↑ limit when a container is near a limit and - with no compose file to read. h (stack harden) fills a gap and L sets or raises limits. stack ls shows the same column.

enter opens the stack's details above its graphs. Sections with nothing in them are left out. ↑ ↓ scroll the details and j k the graphs. The Actions block closes the details with everything the stack can do, views on the left and changes on the right. tab moves into it, the arrows pick and enter runs the item as its key does. A dimmed item says why when you pick it.

Some keys work only in the details. M moves the stack to the other manager, T moves it to the owner's rootless runtime or back, b and t back up and restore-test its database and R restores it from a backup. z rolls back to the last deploy and m shows memory use, in the list too. Each change is a dry run first.

The env editor

v on the Stacks tab opens a stack's env, one row for each variable with its state, its value and the services that use it. The states are set, set, unused, needed (the compose uses it and nothing sets it), compose (a value written in the compose) and image (an image's own default).

enter sets the row's variable and a adds one, the value typed hidden. d removes a set one and e opens the compose in your editor. Changes are held until p shows their plan. z drops the last one and esc all of them. Confirmed, the plan runs as a job (stack env), and a stopped stack is started.

Setting a value written in the compose, or an image's variable the compose doesn't pass, rewrites its line to take the value from the stack's env. Where the line can't take it, enter says why.

A set value shows as ••••••. r shows it until the next key, for 10 seconds at most.