Document use of Cloud Native Buildpacks

dotnet-core/index.html.md.erb → classical/dotnet-core/index.html.md.erb

@@ -153,7 +153,7 @@ To deactivate NuGet package caching:
     ```
     Where `APP-NAME` is the name of your app.
 
-For more information, see [Environment Variables](../../devguide/deploy-apps/manifest.html#env-block) in _Deploying with App Manifests_.
+For more information, see [Environment Variables](../../../devguide/deploy-apps/manifest.html#env-block) in _Deploying with App Manifests_.
 
 
 ## <a id='framework-dependent'></a> Framework dependent deployments

hwc/extension-buildpack.html.md.erb → classical/hwc/extension-buildpack.html.md.erb

@@ -167,6 +167,6 @@ If your extension buildpack does not include the correct dependencies, you recei
 
 If your extension buildpack has executables or scripts that need to be run, you can reference them either in the start command or in profile scripts.
 
-* For more information about the start command, see [command](../../devguide/deploy-apps/manifest.html#start-commands) in <em>Deploying with Application Manifests</em>.
+* For more information about the start command, see [command](../../../devguide/deploy-apps/manifest.html#start-commands) in <em>Deploying with Application Manifests</em>.
 
-* For more information about profile scripts, see [Configure Pre-Runtime Hooks](../../devguide/deploy-apps/deploy-app.html#profile) in <em>Deploying an Application</em>.
+* For more information about profile scripts, see [Configure Pre-Runtime Hooks](../../../devguide/deploy-apps/deploy-app.html#profile) in <em>Deploying an Application</em>.

hwc/index.html.md.erb → classical/hwc/index.html.md.erb

@@ -55,7 +55,7 @@ Most `Web.config` files work immediately with <%= vars.windows_runtime_abbr %>,
 
 - Integrated Windows Authentication (IWA) is not yet supported on <%= vars.windows_runtime_abbr %>.
 - SQL server connection strings must use fully qualified domain names.
-- Place connection string values in environment variables or [user-provided service instances](../../devguide/services/user-provided.html).
+- Place connection string values in environment variables or [user-provided service instances](../../../devguide/services/user-provided.html).
 
 In addition, the [Shadow Copy Setting](#shadow-copy), and [Dynamic and Static HTTP Compression](#http-compression) `Web.config` settings can be customized as needed.
 
@@ -191,7 +191,7 @@ It's preinstalled in the Windows file system.
 With the HWC buildpack you can provide `.profile.bat` scripts with your applications.
 You can use a `.profile.bat` script to perform app-specific initialization tasks. For example, setting custom environment variables.
 
-For information about configuring `.profile.bat` scripts, see [Configure Pre-Runtime Hooks](../../devguide/deploy-apps/deploy-app.html#profile) section of <em>Pushing an App</em>.
+For information about configuring `.profile.bat` scripts, see [Configure Pre-Runtime Hooks](../../../devguide/deploy-apps/deploy-app.html#profile) section of <em>Pushing an App</em>.
 
 ## <a id='help'></a>Buildpack support
 

classical/index.html.md.erb

@@ -0,0 +1,49 @@
+---
+title: Classical buildpacks
+owner: Buildpacks
+---
+
+Buildpacks provide framework and runtime support for your apps. Buildpacks typically examine your apps to
+determine what dependencies to download and how to configure your apps to communicate with bound services.
+
+When you push an app, Cloud Foundry automatically detects an appropriate buildpack for it.
+This buildpack is used to compile or prepare your app for launch.
+
+Cloud Foundry deployments often have limited access to dependencies.
+This limitation occurs when the deployment is behind a firewall, or when administrators want to use local mirrors and proxies. In these circumstances, Cloud Foundry provides a Buildpack Packager app. For more information, see the <a href="https://github.com/cloudfoundry/buildpack-packager">Buildpack Packager</a> repository on GitHub.
+
+## <a id='using-buildpacks'></a> Using buildpacks
+
+The following topics discuss different usage scenarios for buildpacks in Cloud Foundry:
+
+* [How buildpacks work](understand-buildpacks.html)
+
+* [Stack association](stack-association.html)
+
+* [Pushing an app with multiple buildpacks](use-multiple-buildpacks.html)
+
+* [Using a proxy](proxy-usage.html)
+
+* [Supported binary dependencies](supported-binary-dependencies.html)
+
+* [Production server configuration](prod-server.html)
+
+## <a id='system-buildpacks'></a> Cloud Foundry Buildpacks
+
+For information about the existing buildpacks that Cloud Foundry supports, see [CF Buildpack Languages and Sources](system-buildpacks.html).
+
+## <a id='sidecar-buildpacks'></a> Sidecar buildpacks
+
+For information about deploying a sidecar buildpack, see [Sidecar buildpack](sidecar-buildpacks.html).
+
+## <a id='community-buildpacks'></a> Community buildpacks
+
+For a list of unsupported, community created buildpacks, see [Community created](https://github.com/cloudfoundry-community/cf-docs-contrib/wiki/Buildpacks#community-created) section of the _Buildpack information for Cloud Foundry v2_ page in the cf-docs-contrib repository on GitHub.
+
+## <a id='developing-buildpacks'></a> Customizing and developing buildpacks
+
+For information about customizing existing buildpacks and developing new buildpacks, see [Customizing and developing buildpacks](./developing-buildpacks.html).
+
+## <a id='buildpack-ci'></a> Using continuous integration for buildpacks
+
+For information about updating and releasing a new version of a Cloud Foundry buildpack through the Cloud Foundry Buildpacks Team Concourse pipeline, see [Using CI for buildpacks](./buildpack-ci-index.html). You can use this topic as a model when working with Concourse to build, and release new versions of your own buildpacks.

java/getting-started-deploying-apps/gsg-grails.html.md.erb → classical/java/getting-started-deploying-apps/gsg-grails.html.md.erb

@@ -6,7 +6,7 @@ owner: Java
 <%=vars.GSG_intro_sentence%>
 
 This information walks you through deploying a Grails app to Cloud Foundry.
-If you experience a problem following the steps, refer to the <%=vars.known_issues%> or [Troubleshooting Application Deployment and Health](./../../../devguide/deploy-apps/troubleshoot-app-health.html) topics for more information.
+If you experience a problem following the steps, refer to the <%=vars.known_issues%> or [Troubleshooting Application Deployment and Health](./../../../../devguide/deploy-apps/troubleshoot-app-health.html) topics for more information.
 
 If you want to go through this tutorial using the sample app, run <code>git clone https://github.com/cloudfoundry-samples/pong_matcher_grails.git</code> to clone the <code>pong_matcher_grails</code> app from GitHub, and follow the instructions in the Sample app step sections.
 
@@ -20,7 +20,7 @@ This section describes how to deploy a Grails application to Cloud Foundry.
 
 * A Grails app that runs locally on your workstation
 * Intermediate to advanced Grails knowledge
-* The [Cloud Foundry Command Line Interface (cf CLI)](../../../cf-cli/install-go-cli.html)
+* The [Cloud Foundry Command Line Interface (cf CLI)](../../../../cf-cli/install-go-cli.html)
 * JDK 1.7 or 1.8 for Java 7 or 8 configured on your workstation
 
 You can develop Grails applications in Groovy, Java 7 or 8, or any JVM language. The Cloud Foundry Java buildpack uses JDK 1.8, but you can modify the buildpack and the manifest for your app to compile to JDK 1.7 as described in <em>Step 8: Configure the Deployment Manifest</em> of this topic.
@@ -115,7 +115,7 @@ Cloud Foundry supports two types of service instances:
 * Managed services integrate with Cloud Foundry through service brokers that offer services and plans and manage the service calls between Cloud Foundry and a service provider.
 * User-provided service instances enable you to connect your application to pre-provisioned external service instances.
 
-For more information about creating and using service instances, refer to the [Services Overview](./../../../devguide/services/index.html) topic.
+For more information about creating and using service instances, refer to the [Services Overview](./../../../../devguide/services/index.html) topic.
 
 #### Create a service instance
 
@@ -188,7 +188,7 @@ applications:
 
 You can specify deployment options in the `manifest.yml` that the `cf push` command uses when deploying your app.
 
-Refer to the [Deploying with application manifests](../../../devguide/deploy-apps/manifest.html) topic for more information.
+Refer to the [Deploying with application manifests](../../../../devguide/deploy-apps/manifest.html) topic for more information.
 
 You can skip this step. The <code>manifest.yml</code> file for the <code>pong_matcher_grails</code> sample app does not require any additional configuration to deploy the app.
 
@@ -367,7 +367,7 @@ You cannot perform certain tasks in the <%=vars.dev_console_2%> because these ar
 <%=vars.dev_console_note%>
 
 ##<a id='troubleshoot'></a>Troubleshooting
-If your application fails to start, verify that the application starts in your local environment. Refer to the [Troubleshooting Application Deployment and Health](./../../../devguide/deploy-apps/troubleshoot-app-health.html) topic to learn more about troubleshooting.
+If your application fails to start, verify that the application starts in your local environment. Refer to the [Troubleshooting Application Deployment and Health](./../../../../devguide/deploy-apps/troubleshoot-app-health.html) topic to learn more about troubleshooting.
 
 ### App deploy fails
 Even when the deploy fails, the app might exist on Cloud Foundry. Run `cf apps` to review the apps in the currently targeted org and space. You might be able to correct the issue using the <%=vars.dev_console_2%>, or you might have to delete the app and redeploy it.

java/getting-started-deploying-apps/gsg-ratpack.html.md.erb → classical/java/getting-started-deploying-apps/gsg-ratpack.html.md.erb

@@ -6,7 +6,7 @@ owner: Java
 <%=vars.GSG_intro_sentence%>
 
 This information walks you through deploying a Ratpack app to Cloud Foundry.
-If you experience a problem following the steps, check the <%=vars.known_issues%> topic or refer to the [Troubleshooting Application Deployment and Health](./../../../devguide/deploy-apps/troubleshoot-app-health.html) topic.
+If you experience a problem following the steps, check the <%=vars.known_issues%> topic or refer to the [Troubleshooting Application Deployment and Health](./../../../../devguide/deploy-apps/troubleshoot-app-health.html) topic.
 
 Sample app step</strong><br />If you want to go through this tutorial using the sample app, run <code>git clone https://github.com/cloudfoundry-samples/pong_matcher_groovy.git</code> to clone the <code>pong_matcher_groovy</code> app from GitHub, and follow the instructions in the Sample app step sections.
 
@@ -20,7 +20,7 @@ This section describes how to deploy a Ratpack application to Cloud Foundry.
 
 * A Ratpack app that runs locally on your workstation
 * Intermediate to advanced Ratpack knowledge
-* The [Cloud Foundry Command Line Interface (cf CLI)](../../../cf-cli/install-go-cli.html)
+* The [Cloud Foundry Command Line Interface (cf CLI)](../../../../cf-cli/install-go-cli.html)
 * JDK 1.7 or 1.8 for Java 7 or 8 configured on your workstation
 
 You can develop Ratpack applications in Java 7 or 8 or any JVM language. The Cloud Foundry Java buildpack uses JDK 1.8, but you can modify the buildpack and the manifest for your app to compile to JDK 1.7. Refer to Step 8: Configure the Deployment Manifest.
@@ -99,7 +99,7 @@ Cloud Foundry supports the following types of service instances:
 * Managed services integrate with Cloud Foundry through service brokers that offer services and plans and manage the service calls between Cloud Foundry and a service provider.
 * User-provided service instances enable you to connect your application to pre-provisioned external service instances.
 
-For more information about creating and using service instances, refer to the [Services Overview](./../../../devguide/services/index.html) topic.
+For more information about creating and using service instances, refer to the [Services Overview](./../../../../devguide/services/index.html) topic.
 
 #### Creating a service instance
 
@@ -176,7 +176,7 @@ applications:
 
 You can specify deployment options in the `manifest.yml` that the `cf push` command uses when deploying your app.
 
-See [Deploying with application manifests](../../../devguide/deploy-apps/manifest.html) for more information.
+See [Deploying with application manifests](../../../../devguide/deploy-apps/manifest.html) for more information.
 
 You can skip this step. The <code>manifest.yml</code> file for the <code>pong_matcher_groovy</code> sample app does not require any additional configuration to deploy the app.
 
@@ -341,7 +341,7 @@ You cannot perform certain tasks in the <%=vars.dev_console_2%> because these ar
 
 ##<a id='troubleshoot'></a>Troubleshooting
 
-If your application fails to start, verify that the application starts in your local environment. Refer to the [Troubleshooting Application Deployment and Health](./../../../devguide/deploy-apps/troubleshoot-app-health.html) topic to learn more about troubleshooting.
+If your application fails to start, verify that the application starts in your local environment. Refer to the [Troubleshooting Application Deployment and Health](./../../../../devguide/deploy-apps/troubleshoot-app-health.html) topic to learn more about troubleshooting.
 
 ### App deploy fails
 

java/getting-started-deploying-apps/gsg-spring.html.md.erb → classical/java/getting-started-deploying-apps/gsg-spring.html.md.erb

@@ -9,7 +9,7 @@ owner: Java
 
 This guide walks you through deploying a Spring app to Cloud Foundry. You can choose whether to push a sample app, your own app, or both.
 
-If you experience a problem following the steps, see the <%=vars.known_issues%> topic, or refer to the [Troubleshooting Application Deployment and Health](./../../../devguide/deploy-apps/troubleshoot-app-health.html) topic.
+If you experience a problem following the steps, see the <%=vars.known_issues%> topic, or refer to the [Troubleshooting Application Deployment and Health](./../../../../devguide/deploy-apps/troubleshoot-app-health.html) topic.
 
 If you want to go through this tutorial using the sample app, run <code>git
 clone https://github.com/cloudfoundry-samples/pong_matcher_spring</code> to clone the <code>pong_matcher_spring</code> app from GitHub, and
@@ -25,7 +25,7 @@ This section describes how to deploy your Spring application to Cloud Foundry.
 
 * A Spring app that runs locally on your workstation
 * Intermediate to advanced Spring knowledge
-* The [Cloud Foundry Command Line Interface (cf CLI)](../../../cf-cli/install-go-cli.html)
+* The [Cloud Foundry Command Line Interface (cf CLI)](../../../../cf-cli/install-go-cli.html)
 * JDK 1.6, 1.7, or 1.8 for Java 6, 7, or 8 configured on your workstation
 
 The Cloud Foundry Java buildpack uses JDK 1.8, but you can modify the buildpack and the manifest for your app to compile to an earlier version. For more information, see <a href="../../custom.html">Creating custom buildpacks</a>.
@@ -148,7 +148,7 @@ applications:
 
 You can specify deployment options in a manifest file `manifest.yml` that the `cf push` command uses when deploying your app.
 
-Refer to the [Deploying with Application Manifests](../../../devguide/deploy-apps/manifest.html) topic for more information.
+Refer to the [Deploying with Application Manifests](../../../../devguide/deploy-apps/manifest.html) topic for more information.
 
 You can skip this step. The <code>manifest.yml</code> file for the <code>pong_matcher_spring</code> sample app does not require any additional configuration to deploy the app.
 
@@ -313,7 +313,7 @@ You cannot perform certain tasks in the <%=vars.dev_console_2%> because these ar
 
 ## <a id='troubleshoot'></a>Troubleshooting
 
-If your application fails to start, verify that the application starts in your local environment. Refer to the [Troubleshooting Application Deployment and Health](./../../../devguide/deploy-apps/troubleshoot-app-health.html) topic to learn more about troubleshooting.
+If your application fails to start, verify that the application starts in your local environment. Refer to the [Troubleshooting Application Deployment and Health](./../../../../devguide/deploy-apps/troubleshoot-app-health.html) topic to learn more about troubleshooting.
 
 ### App deploy fails
 

java/index.html.md.erb → classical/java/index.html.md.erb

@@ -26,7 +26,7 @@ Once staging completes, the buildpack stops logging then the Loggregator handles
 
 Your application must write to STDOUT or STDERR for its logs to be included in
 the Loggregator stream.
-For more information about logging, see [App Logging in <%= vars.product_short %>](../../devguide/deploy-apps/streaming-logs.html).
+For more information about logging, see [App Logging in <%= vars.product_short %>](../../../devguide/deploy-apps/streaming-logs.html).
 
 ## <a id='bosh-trusted-cert'></a> BOSH custom trusted certificate support