Do
19runbooks
8recent runs
These are the things Kawa is allowed to carry out, and they are the only ones. Each goes down a channel the shops already use — the job queue a manager's panel writes to, or a script that already lives on the server. There is deliberately no box here that runs whatever is typed into it: this page answers on plain HTTP, and such a box would be a root shell on the internet with five tills behind it.
Bring one shop fully up to date each screen is down for about a minute, in turn; the shop cannot print for a few seconds when the hub swaps ← all
Everything a shop runs, in the order that does not break it: check the build against the repository first, then the screens one at a time, then the hub, then the menu. Reads each one back rather than trusting that it worked.
What it will do
1
Is the build newer than the code?
kawa
2
Stop here if that said BEHIND
note
3
What the shop looks like before we touch it
hub
4
Update the screens, one after another
update
5
Let them come back
wait
6
Who is attached now
hub
7
The hub itself
hub-update
8
Give it a moment to unpack
wait
9
Finish the handover it says it did
hub
10
Let the screens find it again — kiosks are the slow ones
wait
11
Hand the menu round
menu-push
12
Everything attached, and what it is holding
hub
13
What the hub is actually serving
hub
14
And which code it is serving it with
hub
15
Read it back
note