Update README with instructions for deploying app

The instructions should be explicit and precise enough for
anyone to deploy to production now. There is a Bamboo job
that should be doing it, but we've had some issue with it and
it often fails, whereas manual pushes always work. You need
a Cloudfoundry account with access to the Sagan organization
to push to production (ask Trevor Marshall).

README.md

@@ -59,5 +59,15 @@ before running `cf push`.
 
 Alternatively you can jar up the app and make it executable in any environment. Care is needed with the includes and excludes:
 
-    $ spring jar --include '+spring/**' --exclude '-**/*.jar,start.jar' start.jar app.groovy
-    $ cf push -p start.jar -p start.jar -n start
+    $ spring jar --include '+spring.zip' start.jar app.groovy
+    $ cf push start -p start.jar -n start-<space>
+    
+Where `<space>` is the name of the space. As a failsafe, and a
+reminder to be explicit, the deployment will fail in production
+without the `-n`. It is needed to select the route because there is a
+manifest that defaults it to `start-development`.
+
+If you are deploying the "legacy" service for STS in production:
+
+    $ cf push start-legacy -p start.jar -n start-legacy
+