From 578fe9cf2a4d8323283359d0663ed2a586ccfc94 Mon Sep 17 00:00:00 2001 From: Ralf Pannemans Date: Fri, 20 Sep 2024 10:18:40 +0200 Subject: [PATCH 1/2] adapted link to changed buildpack structure --- deploy-apps/manifest-attributes.html.md.erb | 2 +- push.html.md.erb | 2 +- sidecars.html.md.erb | 6 +++--- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/deploy-apps/manifest-attributes.html.md.erb b/deploy-apps/manifest-attributes.html.md.erb index df1fce72..85878d69 100644 --- a/deploy-apps/manifest-attributes.html.md.erb +++ b/deploy-apps/manifest-attributes.html.md.erb @@ -156,7 +156,7 @@ You can refer to a buildpack by name in a manifest or a command-line option. The The `-b` command-line flag overrides this attribute. -For more information, see [Pushing an app with multiple buildpacks](../../buildpacks/use-multiple-buildpacks.html). +For more information, see [Pushing an app with multiple buildpacks](../../buildpacks/classical/use-multiple-buildpacks.html). ### command diff --git a/push.html.md.erb b/push.html.md.erb index d7fa41ee..791cdba2 100644 --- a/push.html.md.erb +++ b/push.html.md.erb @@ -17,7 +17,7 @@ These topics contain the procedures for deploying apps with `cf push`: * [Starting, restarting, and restaging Apps](./deploy-apps/start-restart-restage.html) -* [Pushing your app with multiple buildpacks](../buildpacks/use-multiple-buildpacks.html) +* [Pushing your app with multiple buildpacks](../buildpacks/classical/use-multiple-buildpacks.html) * [Pushing an app with multiple processes](./multiple-processes.html) diff --git a/sidecars.html.md.erb b/sidecars.html.md.erb index 6806efe1..6fedb9d2 100644 --- a/sidecars.html.md.erb +++ b/sidecars.html.md.erb @@ -24,7 +24,7 @@ single container on Diego. Both processes within the container undergo health ch You can push sidecar processes with your app by using one of two methods: * Using an app manifest. For instructions, see [Push an app with a sidecar Using an app manifest](#create). -* With a custom buildpack. For instructions, see [Sidecar buildpacks](../buildpacks/sidecar-buildpacks.html). +* With a custom buildpack. For instructions, see [Sidecar buildpacks](../buildpacks/classical/sidecar-buildpacks.html). For additional information about sidecars, see [Sidecars](http://v3-apidocs.cloudfoundry.org/version/release-candidate/#sidecars) in the Cloud Foundry API (CAPI) documentation. @@ -88,7 +88,7 @@ Where: * `START-COMMAND` is the command used to start the sidecar. For example, `./binary` or `java -jar java-file.jar`. You must also allocate memory to sidecars that you push with a custom buildpack. -For more information, see [Sidecar buildpacks](../buildpacks/sidecar-buildpacks.html). +For more information, see [Sidecar buildpacks](../buildpacks/classical/sidecar-buildpacks.html). ### Packaging binaries @@ -459,7 +459,7 @@ next steps: * Use more sophisticated debugging tools * Return the debug information in the HTTP response, rather than logging to STDOUT * Inject the debug sidecar via a [Sidecar -buildpacks](../buildpacks/sidecar-buildpacks.html). For example: +buildpacks](../buildpacks/classical/sidecar-buildpacks.html). For example: [java-debug-buildpack](https://github.com/Gerg/java-debug-buildpack) on GitHub. * Add authentication for the debug sidecar's HTTP route, for instance using an authentication [Route Service](../services/route-services.html). From 3215edfd719e19716bea9d327662f6aa0ccd187d Mon Sep 17 00:00:00 2001 From: Pavel Busko Date: Mon, 30 Sep 2024 14:50:57 +0200 Subject: [PATCH 2/2] Add lifecycle attribute Co-authored-by: Ralf Pannemans --- deploy-apps/manifest-attributes.html.md.erb | 20 +++++++++++++++++++- push.html.md.erb | 2 +- sidecars.html.md.erb | 6 +++--- 3 files changed, 23 insertions(+), 5 deletions(-) diff --git a/deploy-apps/manifest-attributes.html.md.erb b/deploy-apps/manifest-attributes.html.md.erb index 85878d69..8b56875f 100644 --- a/deploy-apps/manifest-attributes.html.md.erb +++ b/deploy-apps/manifest-attributes.html.md.erb @@ -156,7 +156,7 @@ You can refer to a buildpack by name in a manifest or a command-line option. The The `-b` command-line flag overrides this attribute. -For more information, see [Pushing an app with multiple buildpacks](../../buildpacks/classical/use-multiple-buildpacks.html). +For more information, see [Pushing an app with multiple buildpacks](../../buildpacks/use-multiple-buildpacks.html). ### command @@ -368,6 +368,24 @@ The default number of instances is 1. To ensure that platform maintenance does not interrupt your app, <%= vars.recommended_by %> recommends running at least two instances. +### lifecycle + +The `lifecycle` attribute specifies which application lifecycle to use for staging and running the application. Three variants are supported at the moment: + +- [`buildpack`](../../buildpacks/classic.html) +- [`cnb`](../../buildpacks/cnb/index.html) +- [`docker`](push-docker.html) + +For example: + +``` +--- + ... + lifecycle: buildpack +``` + +The default is `buildpack` unless the [`docker`](#docker) attribute is specified. + ### log-rate-limit-per-second The `log-rate-limit-per-second` attribute specifies the log rate limit for all instances of an app. This attribute requires a unit of measurement: `B`, `K`, `KB`, `M`, `MB`, `G`, or `GB`, in either uppercase or lowercase. diff --git a/push.html.md.erb b/push.html.md.erb index 791cdba2..d7fa41ee 100644 --- a/push.html.md.erb +++ b/push.html.md.erb @@ -17,7 +17,7 @@ These topics contain the procedures for deploying apps with `cf push`: * [Starting, restarting, and restaging Apps](./deploy-apps/start-restart-restage.html) -* [Pushing your app with multiple buildpacks](../buildpacks/classical/use-multiple-buildpacks.html) +* [Pushing your app with multiple buildpacks](../buildpacks/use-multiple-buildpacks.html) * [Pushing an app with multiple processes](./multiple-processes.html) diff --git a/sidecars.html.md.erb b/sidecars.html.md.erb index 6fedb9d2..6806efe1 100644 --- a/sidecars.html.md.erb +++ b/sidecars.html.md.erb @@ -24,7 +24,7 @@ single container on Diego. Both processes within the container undergo health ch You can push sidecar processes with your app by using one of two methods: * Using an app manifest. For instructions, see [Push an app with a sidecar Using an app manifest](#create). -* With a custom buildpack. For instructions, see [Sidecar buildpacks](../buildpacks/classical/sidecar-buildpacks.html). +* With a custom buildpack. For instructions, see [Sidecar buildpacks](../buildpacks/sidecar-buildpacks.html). For additional information about sidecars, see [Sidecars](http://v3-apidocs.cloudfoundry.org/version/release-candidate/#sidecars) in the Cloud Foundry API (CAPI) documentation. @@ -88,7 +88,7 @@ Where: * `START-COMMAND` is the command used to start the sidecar. For example, `./binary` or `java -jar java-file.jar`. You must also allocate memory to sidecars that you push with a custom buildpack. -For more information, see [Sidecar buildpacks](../buildpacks/classical/sidecar-buildpacks.html). +For more information, see [Sidecar buildpacks](../buildpacks/sidecar-buildpacks.html). ### Packaging binaries @@ -459,7 +459,7 @@ next steps: * Use more sophisticated debugging tools * Return the debug information in the HTTP response, rather than logging to STDOUT * Inject the debug sidecar via a [Sidecar -buildpacks](../buildpacks/classical/sidecar-buildpacks.html). For example: +buildpacks](../buildpacks/sidecar-buildpacks.html). For example: [java-debug-buildpack](https://github.com/Gerg/java-debug-buildpack) on GitHub. * Add authentication for the debug sidecar's HTTP route, for instance using an authentication [Route Service](../services/route-services.html).