Very crude auto-test harness driving tmux

docs/kubectlrun.md

@@ -136,6 +136,12 @@ We should see the following things:
   kubectl logs deploy/pingpong --tail 1 --follow
   ```
 
+<!--
+```keys
+^C
+```
+-->
+
 ]
 
 ---
@@ -174,6 +180,12 @@ We could! But the *deployment* would notice it right away, and scale back to the
   kubectl get pods -w
   ```
 
+<!--
+```keys
+^C
+```
+-->
+
 - Destroy a pod:
   ```bash
   kubectl delete pod pingpong-yyyy

docs/ourapponkube.md

@@ -184,6 +184,7 @@ The curl command should now output:
 
 - Build and push the images:
   ```bash
+  export REGISTRY
   docker-compose -f dockercoins.yml build
   docker-compose -f dockercoins.yml push
   ```
@@ -301,6 +302,12 @@ services:
 
   (Give it about 10 seconds to recover)
 
+<!--
+```keys
+^C
+```
+-->
+
 ]
 
 --

docs/prereqs-k8s.md

@@ -92,18 +92,6 @@ class: in-person
 for N in $(seq 1 5); do
   ssh -o StrictHostKeyChecking=no node$N true
 done
-for N in $(seq 1 5); do
-  (.
-  docker-machine rm -f node$N
-  ssh node$N "docker ps -aq | xargs -r docker rm -f"
-  ssh node$N sudo rm -f /etc/systemd/system/docker.service
-  ssh node$N sudo systemctl daemon-reload
-  echo Restarting node$N.
-  ssh node$N sudo systemctl restart docker
-  echo Restarted node$N.
-  ) &
-done
-wait
 ```
 -->
 
@@ -115,8 +103,8 @@ wait
 - Type `exit` or `^D` to come back to node1
 
 <!--
-```meta
-^D
+```keys
+exit
 ```
 -->
 

docs/prereqs.md

@@ -114,18 +114,6 @@ class: in-person
 for N in $(seq 1 5); do
   ssh -o StrictHostKeyChecking=no node$N true
 done
-for N in $(seq 1 5); do
-  (.
-  docker-machine rm -f node$N
-  ssh node$N "docker ps -aq | xargs -r docker rm -f"
-  ssh node$N sudo rm -f /etc/systemd/system/docker.service
-  ssh node$N sudo systemctl daemon-reload
-  echo Restarting node$N.
-  ssh node$N sudo systemctl restart docker
-  echo Restarted node$N.
-  ) &
-done
-wait
 ```
 -->
 
@@ -137,8 +125,8 @@ wait
 - Type `exit` or `^D` to come back to node1
 
 <!--
-```meta
-^D
+```keys
+exit
 ```
 -->
 

docs/rollout.md

@@ -58,7 +58,8 @@
 
 - Build a new tag and push it to the registry:
   ```bash
-  export REGISTRY=localhost:3xxxx TAG=v0.2
+  #export REGISTRY=localhost:3xxxx
+  export TAG=v0.2
   docker-compose -f dockercoins.yml build
   docker-compose -f dockercoins.yml push
   ```
@@ -126,6 +127,12 @@ Our rollout is stuck. However, the app is not dead (just 10% slower).
 
 .exercise[
 
+<!--
+```keys
+^C
+```
+-->
+
 - Cancel the deployment and wait for the dust to settle down:
   ```bash
   kubectl rollout undo deploy worker

docs/sampleapp.md

@@ -161,9 +161,14 @@ and displays aggregated logs.
 - Stop the application by hitting `^C`
 
 <!--
-```meta
+```wait
+units of work done
+```
+
+```keys
 ^C
 ```
+
 -->
 
 ]
@@ -216,7 +221,7 @@ class: extra-details
   ```
 
 <!--
-```meta
+```keys
 ^C
 ```
 -->
@@ -362,13 +367,6 @@ We have available resources.
 
 - Look at the impact on CPU load and memory usage
 
-<!--
-```bash
-sleep 5
-killall docker-compose
-```
--->
-
 ]
 
 ---