anchor.diff:  $ rake test_vm
   </pre>
   
  -VM creation is likely to take a while.
  -
  -If the `rake test_vm` step fails and you see an error similar to "undefined method 'configure' for Vagrant" or "found character that cannot start any token while scanning for the next token," you are using a unsupported version of Vagrant. Install Vagrant version 1.1 or higher.
  +Failure of the `rake test_vm` step followed by an error similar to "undefined method 'configure' for Vagrant" or "found character that cannot start any token while scanning for the next token" can result from using an unsupported version of Vagrant. Ensure you have installed Vagrant version 1.1 or higher.
   
   <pre class="terminal">
   # initialize the test VM
  
positive.code: 
  The DEA also checks for a `AppState` object for the application.
  
  
  ## <a id='usage'></a>Usage ##
  
  You can run the dea executable at the command line by passing the path to the DEA configuration file:
  
  <pre class="terminal">
  $ bin/dea config/dea.yml
  
negative.code: 
  ## <a id='dea-configuration'></a>DEA Configuration ##
  
  DEA behavior is configured in the `dea.yml` file.
  
  The following is a partial list of the keys that the DEA reads from the YAML file:
  
  * `logging`: A [Steno configuration](http://github.com/cloudfoundry/steno#from-yaml-file)
  * `nats_uri`: A URI of the form `nats://host:port` that the DEA uses to connect to NATS
  * `warden_socket`: The path to a UNIX domain socket that the DEA uses to communicate to a Warden server.
  
  A sample `dea.yml` file follows:
  
  <p class="note"><strong>Note</strong>: See <a href='https://github.com/cloudfoundry/dea_ng/blob/master/lib/dea/config.rb'>https://github.com/cloudfoundry/dea_ng/blob/master/lib/dea/config.rb</a> for optional configuration keys.</p>
  
  ```yaml
  
  # See src/lib/dea/config.rb for optional config values.
  
  # Base directory for dea. Application directories, DEA temp files, etc. are all relative to this.
  base_dir: /tmp/dea_ng
  
  logging:
  