Journal

The journal lists every change laraport made, newest first. Use it to answer “what did I run on production yesterday?” or “did that migration finish?”.

Opening it

• h on the home screen shows the journal of every server.
• Journal in the command palette of a container list (ctrl+k) shows that server only. There, a switches between that server and every server.

Each line shows when, the server and container, the action and how it ended. enter shows one entry in full, with its whole command, SQL or path. r reads the journal again.

What it records

An action is written when it starts, with:

• the server and the container;
• the action and its command, SQL or file path;
• then how it ended: finished, failed with the error, stopped before the end, 1 row(s) changed, or saved with the backup’s name.

Because the entry is written before the action runs, a crash or a dropped connection midway still leaves it on record.

Recorded:

• commands other than known reads (Artisan, Composer, npm, your commands, the custom command), deploy commands and prunes;
• container actions (start, stop, restart, remove) and Swarm and Compose actions, with the command that ran;
• deleted Redis keys;
• SQL other than a single SELECT, and table edits;
• file saves and uploads;
• dump restores;
• Tinker runs, shells and tunnels.

Not recorded:

• reads: logs, tables, SELECT queries, inspect, downloads;
• actions a read-only server refused, since nothing ran.

Where it is kept

The journal stays on your computer, in ~/.config/laraport/journal.jsonl:

• mode 0600, one JSON line per action;
• past 4 MB it is cut back to its newer half;
• passwords never reach it: they travel over stdin, not in commands.

The servers keep no trace of it.