removing sync'd folder for /vagrant

change identity file default to none

removing check for git identity

typo

typo

adding python-yaml for dumping vars

certs settings changes for local disk generation

adding var dump var

adding template for certs

adding certs to default sites

adding 400 condition to the certs nginx template

updating update script for certs, removing discern

adding cert to help

giving www-data write permission to the web root

typo

adding download url

fixing web root

adding certs download url

adding more config for cert template dir, verify url

moving extra vars into the vagrantfile

adding verify url to vagrantfile

syntax

look for valid.html

adding ownertrust export

adding the trust import

removing skip-tags for reconfigure

upgrading to latest released ansible

adding carriage return to owner trust

setting cert urls in extra vars

moving extra vars to vagrantfile

adding new accept_hostkey parameter to all git calls

set key_file

changing dir for userknownhostsfile

adding more verbosity

changing knownhostsfile in environment

don't use userknownhostsfile

setting accept_hostkey back to yes

adding .ssh dirs for the 1.5 git module

adding certs nginx site

Explicitly set ssh to insecure private key.  It is default but sometimes does not work and requires public key

The LC_ALL environment variable is set to en_US in /etc/default/locale
in the precise32 vagrant box, see:

https://github.com/mitchellh/vagrant/issues/1188

When running the python unit tests in the devstack machine, several of the
tests fail with a UnicodeEncodeError when trying to create folders with names
that contain non-ascii characters.

Explicitly setting LC_ALL to en_US.UTF-8 before running the tests fixes this issue,
but it would be nice if the box was set up with the en_US.UTF-8 locale by default.

Wiki will need to be updated to reflect this addition

Added script to auto install vagrant-vbguest if it's needed

This mounts the "themes" directory on the host.  This will enable people
who have configured "stanford-style" themes to check out their themes on
the host and have it useable in the devstack.

Two things are a bit odd about this that are worth highlighting.

1. For people not using Stanford-style theming, which are most
   developers and certainly everyone at edX.org, this is a wasted
   export.  It doesn't do any harm, but would it be confusing?  I
   think that's OK.

2. The provision steps checks out the other repos that you need
   (edx-platform, cs_comment_service, etc.).  We're not checking out
   the theme repo ourselves here, counting on the user to do so
   yourself later.  I know this isn't consistent, but I couldn't
   plumb through the theming stuff into the rest of devstack
   provision, at least not right now.

Make the configuration versions of the Vagrantfile more explicit.