By setting NGINX_ENABLE_SSL ssl this will be enabled in
the nginx configuration for those roles that support
it, currently just the lms and cms.

To use a custom key/cert set the following vars:

* NGINX_SSL_CERTIFICATE
* NGINX_SSL_KEY

Note that there is only one ssl certificate and key
per nginx install, this is because of the way nginx
is setup (independent of the other roles).

We could enable it for different roles though they would
share the same certificate.

Instead of enabling basic auth per role this makes it
an nginx parameter which makes more sense for sandboxes
and probably other servers where we want basic auth turned on

Conflicts:
	playbooks/roles/common/handlers/main.yml

removing nginx setup from individual roles

These are some minimal changes to support 1.3, does not yet include role
dependencies.

If the nginx play is called with the nginx_conf varialble, then expect
to find in {{secure_dir}}/files/nginx.conf and copy it over.  If not set
then the default one already there will be sufficient.

One comes with the standard installation, overwrite with our own,
provided in {{secure_dir}}/files.

To support variations on our local LMS sites files it is helpful to have
subdirectories where we can store variations.  At Stanford I'm using
this so I can store carnegie/lms.j2, a variation on our normal lms.j2.

To use you can call the role like this:
    - {'role': 'edxapp', 'openid_workaround': true, 'template_subdir': 'carnegie'}
This would be from your main playbook file, in my case
edx-west/carnegie-prod-app.yml.

While in here I noticed we weren't setting owner or perms on the
sites-available/XX files, fix that.