anchor.diff:  This completes this section. (I am not pulling your work back into the main lab.)
   
   There is much to learn about git and this lab is not intended to be a full tutorial, but rather means to an end, and a quick flavor of the techniques. We will cover further aspects as necessary.
  +If you are looking for a short introductory course on git, check out the free online training course at link:http://gitreal.codeschool.com/[Git Real by Code School].
   
   == 4. Automated provisioning and infrastructure as code
   
  
positive.code: 
      vagrant@XXXXX:~/vagrant$ ./YourStudentID-Lab02.sh  <- notice the "./"
  
  Create your script.
  
      vagrant@XXXXX:~/vagrant$ nano YourStudentID-Lab02.sh
  
  _add the necessary commands so that the script does what it needs to do_
  
  Oops, something seems to be wrong when you run it:
  
  
negative.code: 
  Re-commit your Vagrantfile and push it back to origin.
  
  Finally, issue a pull request for me to review your work.
  
  Discuss:
  
  - Why can you commit to git on the VM without initializing the repo there? You had to at least set up your name and email. Hint: Think about the virtual directory mapping and execute the comand "ls -al" on the /vagrant directory in the VM.
  - How are git and tree getting installed, since you don't say "sudo vagrant up"?
  
  That is the end of this lab. Congratulations, this was a lot of work. Next week, we will start working on the the continuous integration pipeline with git, Java, JUnit, Tomcat, and Ant.
  