distill what are the ingredients for a new guide, then create template

[jspaaks]

e.g.

1. install provisioning tools Ansible, ssh, putty, WSL, etc
   • install options, e.g. Ansible from package manager, PPA, pip, or docker
2. generating ssh keys, getting them to the server
3. homogenize use of ansible.cfg, mention it, explain it
4. homogenize use of hosts, mention it, explain it
5. homogenize use of elevated permissions
6. homogenize connection options, --ssh-extra-args, ansible_user, etc
7. in playbooks, homogenize use of roles v shell tasks
8. homogenize the directory structure of the various examples that one can find under a given combination of client OS and server hardware. e.g. runner and install-cudahere. Besides runner, we could have something like cuda, opencl, openmp, mpi, slurm. These could be mixin-like documents so users can do at least runner, but then do e.g. cuda and slurm as well, if their use case requires it.

This stuff should be decided on, then put into a template that people can use such that if someone makes a contribution for new hardware, say, AWS, they know what should be in the readme.

[jspaaks]

PR WIP #85

[jspaaks]

done. closing