$ spring run app.groovy

$ $ cf push cf-scale-boot -m 512M -b https://github.com/cloudfoundry/java-buildpack -n cf-scale-boot-a123z

1. Push the application as-is, with blue appended to the application name. Use '-n' to define a unique HOSTNAME:

   $ cf push cf-bg-demo-blue -m 512M -b https://github.com/cloudfoundry/java-buildpack -n cf-bg-demo-blue-a123z

2. Map a ``zero downtime'' route to the application and use '-n' to define a unique HOSTNAME:

   cf map-route cf-bg-demo-blue cfapps.io -n cf-bg-demo-a123z

   Visit your application in the browser using your zero downtime route to see that it is working.

3. Modify app.groovy to use the color green (line 8):

   model['color'] = 'green'

4. Push the modified application, with green appended to the application name and again use '-n' to define a unique HOSTNAME:

   $ cf push cf-bg-demo-green -m 512M -b https://github.com/cloudfoundry/java-buildpack -n cf-bg-demo-green-a123z

5. Map the ``zero downtime'' route to the modified application, including the HOSTNAME suffix you added in Step 2:

   cf map-route cf-bg-demo-green cfapps.io -n cf-bg-demo-a123z

   Visit your application in the browser using your zero downtime route to see that the platform is load balancing between the two instances.

6. Un-map the ``zero downtime'' route from the original application, including the HOSTNAME suffix you added in Step 2:

   cf unmap-route cf-bg-demo-blue cfapps.io -n cf-bg-demo-a123z

   Visit your application in the browser using your zero downtime route to see that only the modified application is now in play.