document automation workflow

[vpnagraj]

getting closer to a first pass at pipeline automation (see #23 #24 #25 )

as we close out those issues i need to:

• [x] document the automation workflow narratively
• [x] make a diagram of resources
• [ ] check with others if to see if they're interested in trying the automation pipeline

[vpnagraj]

this is now in progress. first working draft of the workflow diagram:

ill be adding some numerical indicators for steps in the process. and those will line up to a narrative caption. but for an initial draft, i think this does a fair job of illustrating the proposed automation pipeline.

note that some of those connections/resources will change as we move forward with other parts of the project. for example, if we release focustools (or at least make the repo public) there will be no need to store the built package in S3 (we can install directly from GH via the bootstrapping script)

also, some of the resources there havent been built quite yet. for example, the second ec2 is a potential shiny app instance (#22 ). currently the user would download directly from s3 instead of through that second instance.

more on this thread in the coming days ...

cc @stephenturner

[vpnagraj]

workflow documented. i'll find a time to demo with those interested.