Until now it's only been used for clustered deployment,
but it works fine in single-instance mode, too.

This solves the problem for installations failing with this message:
"msg: Failed to validate the SSL certificate for download.elasticsearch.org:443. Use validate_certs=no or make sure your managed systems have a valid CA certificate installed. Paths checked for this platform: /etc/ssl/certs, /etc/pki/ca-trust/extracted/pem, /etc/pki/tls/certs, /usr/share/ca-certificates/cacert.org, /etc/ansible"

I recently had a build where elasticsearch hadn't auto started so
I added that check here.

* consistent jinja variable syntax
* comment blocks on the tasks/main.yml files
* some syntax errors, variable name issues
* indenting, breaking up long lines
* various bug fixes

works from scratch on gce and better generalization

missed file

changing user for checkout task

reverting path change

fix typo

fully working on debian

working upstart

moving env from bashrc

removing unused template

adding template for ruby env setting

removing unused template

removing forum and ruby env from bashrc, general cleanup