anchor.diff:  * various http://www.jetbrains.com/[JetBrains IDEs]
   * https://github.com/jkbrzt/httpie[httpie] - a more friendly alternative to cURL and wget
   
  -=== Different Windowing Systems
  -CAUTION: Currently in incubation.
  -
  -We have branches that use different window managers that may appeal to you.  Use Git to switch to appropriate branch and run `vagrant up` to try it out.
  -
  -* Xubuntu
  -* Lubuntu
  -* Gnome
  -* Kubuntu
  -* Mate
  -* Cinnamon
  -* Unity
  -
  -=== SSH Jump Servers
  -Some personal and corporate plays install a custom SSH configuration which simplifies access to private machines.  Look in `~/.ssh/config` to see what your configuration looks likes.  When I want to access an Amazon EC2 instance in a private subnet, I have to proxy through a Bastion, aka Jump Server, box.  To do that I need to edit the configuration file to make sure I have the proper public address of the Bastion box.
  -
  -```
  -Host bastion
  -    User ec2-user
  -    HostName ec2-54-218-52-2.us-west-2.compute.amazonaws.com
  -    IdentityFile ~/Bitbucket/Operations/aws-ssh-keys/us-west-2/asgard-lite-test.pem
  -    ForwardAgent yes
  -
  -Host 10.0.*.*
  -    User ec2-user
  -    IdentityFile ~/Bitbucket/Operations/aws-ssh-keys/us-west-2/asgard-lite-test.pem
  -    ProxyCommand ssh bastion -W %h:%p
  -    ExitOnForwardFailure yes
  -```
  -
  -To test out the configuration, try `ssh bastion`.  Once that is working, try connecting to an internal box `ssh 10.20.30.40` and see if that works.  The same setup works for accessing your home network.
  -
   == Troubleshooting
   
   === My Favorite App Is Missing!
  
positive.code: === Installed Infrastructure
  Docker containers running common infrastructure are installed in `/home/vagrant/bin/servers`.  Look at the `docker-compose.yml` file to see what services are currently available to use.  Run the `start.sh` script to install and run the servers.  You can also start up a single server, eg `docker-compose up -d mongodb`.
  
  === Juniper VPN Support
  
  1. Change into the `~/vagrant/VPN` folder
  1. edit `jvpn.ini` changing the `username` and `password` values
  1. run `./vpn.sh` to start your session
  1. `ctrl-c` to exit the session
  
  === Docker-based IDEs
  We've deprecated the use of Docker-based IDEs.  We've found that projects that produce and consume Docker images can be challenging when running from within a container.  If Docker in Docker ever becomes mainstream, we'll look into switching back.
  
  === Applying Your Company Specific Customizations
  The system will look for an environment variable named `CORPORATE_PLAYS`.  If the shell running Vagrant specifies the variable such that it points to an Ansible project on GitHub, the plays will be run and the changes applied.  For example `export CORPORATE_PLAYS=kurron/ansible-pull-transparent.git` will result in https://github.com/kurron/ansible-pull-transparent.git[this playbook] getting run.  If the environment variable does not exist, the custom provisioning step is not run.
  
  === Applying Your Personal Customizations
  The system will look for an environment variable named `USER_PLAYS`.  If the shell running Vagrant specifies the variable such that it points to an Ansible project on GitHub, the plays will be run and the changes applied.  For example `export USER_PLAYS=myaccount/my-custom-tweaks.git` will result in https://github.com/myaccount/my-custom-tweaks[this playbook] getting run.  If the environment variable does not exist, the custom provisioning step is not run.
  
  === Customizations: Linux Example
  1. create and/or edit `~/.bash_profile`
  
negative.code: 
  === My Git settings are all wrong!
  You need to specify a custom Git configuration file.  The best way to do that is to create and apply your own customizations. See the <<Applying Your Own Customizations>> section above on how to do that.
  
  === I'm running Windows 7 and Vagrant hangs!
  You need to install a current version of https://www.microsoft.com/en-us/download/details.aspx?id=40855[Windows Management Framework] and then reboot your machine.  Apparently, there is a compatibility issue older PowerShell and newer Vagrant versions.
  