This topic describes the additional environment variables provided by the Ruby buildpack.

For more information about the standard environment variables provided by <%=vars.product_full%>, see the [Cloud Foundry Environment Variables](../../devguide/deploy-apps/environment-variable.html) topic.

## Ruby Buildpack Environment Variables ##

The following table describes the environment variables provided by the Ruby buildpack.

<td>The path to the Gemfile for the app. Example: <code>BUNDLE_GEMFILE:/home/vcap/app/Gemfile</code></td>

</tr>

<tr>

<td><code>BUNDLE_WITHOUT</code></td>

<td>Instructs Cloud Foundry to skip gem installation in excluded groups. Use this with Rails applications, where "assets" and "development" gem groups

typically contain gems that are not needed when the app runs in production. Example: <code>BUNDLE_WITHOUT=assets</code>

</td>

</tr>

<tr>

<td><code>DATABASE_URL</code></td>

<td>Cloud Foundry examines the <code>database_uri</code> for bound services to see if they match known database types. If known relational database services are bound to the app, then the <code>DATABASE_URL</code> environment variable is set to the first services in the list.

<br><br>

If your application requires that <code>DATABASE_URL</code> is set to the connection string for your service, and Cloud Foundry does not set it, use the Cloud Foundry Command Line Interface (cf CLI) <code>cf set-env</code> command to set this variable manually. Example: <preclass='terminal'>$ cf set-env my-app DATABASE_URL mysql://example-database-connection-string</pre></td>