The desktop app (after 1.0)#
The app is for people who never open a terminal. It is one window over the same Go code the parity command runs:
each button calls the code its command calls, and nothing in the window decides anything on its own. So the window
and the command cannot disagree, and a screen always says which command it matches ("In a terminal:
parity status").
Your app, up and matching#
The app's home shows one app: its state, Start or Stop (one button), Open in browser and Run test, the address, and the same side by side mirror the front page shows, one row per fact, reading "Matches Citadel." when every row does.
parity status.Logs#
The Logs tab is parity logs -f with a filter: all of it, or only the app, the proxy, MySQL or Parity's own lines.
The local passwords Parity made for the app show as hidden, here as in the terminal.
parity.json, without a text editor#
The parity.json tab sets what the file sets: how sign-in works here (none, SESAME's fake sign-in, or Wayne State CAS as on Citadel), and the cron entries Citadel runs in the app container. The whole file sits under it, to read or copy; the parity.json reference covers every key.
The rest#
- Check this computer is the first screen: the same checks as
parity check. - Add an app proposes the parity.json
parity initwould write and writes nothing until you say so. - Settings picks the engine (Docker or Podman), checks the ports, and gets or verifies Citadel's images with the
same steps as
parity image getandparity image verify. - Ctrl K lists every command, each with the
paritycommand it matches.
The front page shows each of these next to its terminal printout: Check, then up.