Many bugfixes, now passes the `vagrant destroy && vagrant up` test:

-Sync folder '.' instead of '..'
-Pip install from apt, immediatly self-upgrade with pip
-virtualenv install from pip instead of apt
-Removed references to broken paths
-Updated adsabs submodule commit
-------
These changes make the provisioning functional without changing the strategy. However, I think that the following should be changed to make this workflow more robust:

1. Don't split up provisioning between the Vagrantfile (inline shell) and Puppet. Puppet is your provisioner, vagrant should just create the VM.
2. Don't use submodule. Instead, use Puppet to clone the relevant repos.
3. (Eventually) move away from fabric. Puppet can do server and application provisioning, and having less dependencies is better.