There is a very crude drush command included with the
configuration_log module that I used for the demo - basically that was
just running in a loop.
The git repo with the recorder branch was under the home directory
of the cloud site user, hence I could just pull from it using ssh.
For a robust solution, we'll need to build up e.g. a module or
script that creates a new recorder branch when a configuration import
happens, and build better daemon or queue and queue-processing
More information about text formats