anchor.diff:        - name: jsonlite
   </pre>
   
  -Provide the vendored packages into a `vendor_r` directory at the root of your app. This directory is named as such so as not to conflict with vendor directories of other languages, such as python.
   
   `cf push` uploads your vendored dependencies. The buildpack installs them directly from the `vendor_r/` directory.
   
  +Example app directory tree:
  +
  +```
  +├── r.yml
  +├── simple-app.r
  +└── vendor_r
  +    └── src
  +        └── contrib
  +            ├── PACKAGES
  +            ├── PACKAGES.gz
  +            ├── jsonlite_1.5.tar.gz
  +            └── stringr_1.3.1.tar.gz
  +```
   
   ## <a id='proxy_support'></a> Proxy Support
   
  
positive.code: 
  - Specify a start command with `-c`:
  
      <pre class="terminal">
      $ cf push r-app -c "R -f simple.r"
      </pre>
  
  - Specify a start command in the application manifest by setting the `command` attribute. For more information, see the [Deploying with Application Manifests](../../devguide/deploy-apps/manifest.html#start-commands) topic.
  
  ## <a id='vendoring'></a> Specifying App Dependencies
  
  As of v0.0.5, the following packages are provided by the buildpack:
  
  
negative.code: 
  Join the #buildpacks channel in our [Slack community](http://slack.cloudfoundry.org/) if you need any further assistance.
  
  For more information about using and extending the R buildpack in Cloud Foundry, see the [R-buildpack GitHub repository](https://github.com/cloudfoundry/r-buildpack).
  
  You can find current information about this buildpack on the [R buildpack
  release page](https://github.com/cloudfoundry/r-buildpack/releases) in GitHub.
  