Ensure that chosen installation framework is automation ready

[DarwinJS]

I have been doing the chocolatey package and just wanted to express a requirement that if an installer is eventually created by this project that it should be automation ready.

This would seem to include as least:

1. choosing a framework that has command line automation capabilities.
2. ensuring that common customization requirements are instrumented to be exposed on the command line (e.g. if "generate server keys" is an option in the interactive installer, then there should be an install parameter that exposes it as well. Same with an option on whether or not to install the sshd server)
3. documenting installation automation parameters.

In addition to just being a best practice, this would allow me to conform the current features supported in the chocolatey package to use the formal installer immediately upon release.

[manojampalam]

Tagging "bug". Will be tracked as part of setup work