anchor.diff:  The application can operate in multiple different profiles according to the location (and presence) of the UAA server and the Login application.
   By default, the application looks for a UAA on `localhost:8080/uaa`, but you can change this by setting an environment variable (or System property) called `UAA_PROFILE`.
   In the application source code (`samples/app/src/main/resources`), you will find multiple properties files pre-configured with different likely locations for those servers.
  -They are all in the form `application-<UAA_PROFILE>.properties`.
  +They are all in the form `application-UAA_PROFILE.properties`.
   The naming convention adopted is that the `UAA_PROFILE` is `local` for the localhost deployment, `vcap` for a `vcap.me` deployment, and `staging` for a staging deployment.
   The profile names are double-barreled (e.g. `local-vcap` when the login server is in a different location than the UAA server).
   
  -#### Use Cases ####
  +##### Use Cases #####
   
   1. See all apps
   
  
positive.code:     ${UAA_CONFIG_URL}
  ```
  
  ### <a id='gradle-test'></a>Test with PostgreSQL or MySQL ##
  
  The default UAA unit tests (`./gradlew test`) use hsqldb.
  
  
negative.code: $ echo "spring_profiles: postgresql,default" > src/main/resources/uaa.yml
  $ ./gradlew run
  </pre>
  
  To bootstrap a microcloud-type environment, you need an admin client; there is a database initializer component that inserts one.
  If the default profile is active (i.e. not `postgresql`), there is also a `cf` CLI client so that the gem login works out of the box.
  