anchor.diff:  
   	App started
   
  -	Showing health and status for app my-app in org example-org / space development as a.user@<%=vars.app_domain%>...
  +	Showing health and status for app my-app-1234 in org example-org / space development as a.user@<%=vars.app_domain%>...
   	OK
   
   	requested state: started
   	instances: 1/1
   	usage: 1G x 1 instances
  -	urls: my-app.<%=vars.app_domain%>
  +	urls: my-app-1234.<%=vars.app_domain%>
   
   	     state     since                    cpu    memory        disk
   	#0   running   2014-01-24 05:07:18 PM   0.0%   18.5M of 1G   52.5M of 1G
  
positive.code:   - [Considerations for Designing and Running an App in the Cloud](./prepare-to-deploy.html)
    - Any [Buildpacks](../../buildpacks/index.html) guides specific to your app language or framework, such as [Getting Started Deploying Ruby on Rails Apps](../../buildpacks/ruby/gsg-ror.html)
  
  * All required app resources are uploaded.
  For example, you may need to include a database driver.
  
  * Extraneous files and artifacts are excluded from upload.
  You should explicitly exclude extraneous files that reside within your
  app directory structure, particularly if your app is large.
  
  * Every service that your app needs has an instance that it can access, for example running in the same space.
  
  * Your <%= vars.product_short %> installation supports the type of app you are going to
  push, or you have the URL of an externally-available buildpack that can stage
  the app.
  
  * You have all of the following:
    - The API endpoint for your <%= vars.product_short %> installation. Also known as the target
  URL, this is <%=vars.api_endpoint%>.
    - Your username and password for your <%= vars.product_short %> installation.
    - The organization and space where you want to push your app.
  A <%= vars.product_short %> workspace is organized into organizations, and within them,
  spaces.
  As a <%= vars.product_short %> user, you may have access to one or more organizations and
  spaces.
  
  ## <a id='options'></a>Push Options
  
  Before you push an app, you need to collect basic field values and decide on some larger options.
  
  ### <a name='basic'></a>Basic Fields
  
  Before you push an app, you need values for the following fields, unless you want the defaults:
  
  
negative.code: The following session illustrates  how <%= vars.product_short %> assigns default values
  to app when given a `cf push` command.
  
  <pre class="terminal">
  	$ cf push my-app-1234
  	Creating app my-app-1234 in org example-org / space development as a.user@<%=vars.app_domain%>...
  	OK
  
  	Creating route my-app-1234.<%=vars.app_domain%>...
  	OK
  
  	Binding my-app-1234.<%=vars.app_domain%> to my-app-1234...
  	OK
  
  	Uploading my-app-1234...
  	Uploading app: 560.1K, 9 files
  	OK
  
  	Starting app my-app-1234 in org example-org / space development as a.user@<%= vars.app_domain %>...
  	-----> Downloaded app package (552K)
  	OK
  	-----> Using Ruby version: ruby-1.9.3
  