Tutorial

Manage Docker Compose from iPhone.

This guide shows which part is saved in sshChat and which part runs on the server. The goal is a clean mobile runbook, not retyping long Docker commands.

Step 1 of 4Waiting for confirmation

Step 1: Save Docker commands in the catalog

sshChat AppRemote Server
Where this happens

You create the saved commands in sshChat. They execute later on the server that runs Docker Compose.

Type these as saved commands
docker compose ps
docker compose up -d
docker compose restart api
docker compose logs --tail 100 web
How to name them

Use short titles like PS, Up Detached, Restart API, and Logs Web.

Step 2: Mark long-running Docker commands for Stream Mode

sshChat AppRemote Server
Where this happens

You toggle Stream Mode in the saved command entry inside sshChat.

Good Stream Mode commands
docker compose build
docker compose up
Why

These commands keep producing output. Stream Mode lets you watch progress instead of waiting for one big result at the end.

Step 3: Keep snapshots in normal mode

sshChat AppRemote Server
Where this happens

You run these from sshChat, but they should finish quickly on the server.

Use normal mode for
docker compose ps
docker compose logs --tail 100 web
Why

Short snapshots keep the chat clean and are easier to scan later in history.

Step 4: Turn Docker into a mobile runbook

sshChat App
Where this happens

Inside the catalog editor in sshChat.

What to organize

Create one category called Docker or Production, then order the commands by the way you normally triage issues: status, logs, restart, build.

Result

You can manage Compose from the phone with taps instead of writing shell syntax every time.