* Move sudo:True out of each task and into the playbook, since it's a
  playbook-level variable
* Removal of a couple debian package installs from common that are also
  being installed in the role where they're needed
* Re-correction of /etc/git-identity permissions
* Other cleanups (whitespace issues, etc.)

* Removes HTTP basic auth

* Enable npm role
* Minor edits to debian dependency list
* Change treatment of a few files and directories

* I've moved the example secure directory to playbooks/secure_example,
  the directory structure in your secure repo should mirror that in
  secure_example/
* If you run the lms role without a valid git-identity file it will
  fail, there is an empty file checked into the secure_example dir
* Using GIT_SSH env for git checkout, we will also need to use that
  for pip installs that use git if there are private repos in
  requirements.

By default it installs 1.9.3-p374 in /opt/www/.rbenv and gems go
in /opt/www/.gem, which replicates the vagrant box

Also changed top level playbook ymlv var search to follow a path, first
over {{ secure_file_dir }} set in group_vars/all then at
vars/secure_default

var empty, so no actual users are created

This keeps vars that are specific to roles with the role, not
very well documented except in the playbook example here:
https://github.com/ansible/ansible/blob/devel/examples/playbooks/roletest.yml

This makes playbooks more concise since you do not have to explicitely
include vars for each roles, var_files will still override any of the
default values in <role>/vars/main.yml

* Created new directory structure outlined in the README
* Created the LMS role which for now just creates teh application config
files
* Created the common role
* Updated the cf playbook to accept arguments