From 4c7092c986052f0f3f03ae4d622b39af3c104978 Mon Sep 17 00:00:00 2001 From: Hanan Younes Date: Wed, 16 Oct 2024 21:20:55 -0400 Subject: [PATCH] adds reviewer code suggestions Signed-off-by: Hanan Younes --- .../for-platform-operators/tutorials/lifecycle/_index.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/content/docs/for-platform-operators/tutorials/lifecycle/_index.md b/content/docs/for-platform-operators/tutorials/lifecycle/_index.md index 29602fc24..0a09a2d74 100644 --- a/content/docs/for-platform-operators/tutorials/lifecycle/_index.md +++ b/content/docs/for-platform-operators/tutorials/lifecycle/_index.md @@ -84,9 +84,11 @@ Let's expand each `lifecycle` phase to explain how the `lifecycle` orchestrates The `analyze` phase runs before the `detect` phase in order to validate registry access for all images used during the `build` as early as possible. In this way it provides faster failures for end users. -Prior to executing `/cnb/lifecycle/analyzer`, you need to create two directories in the `root` directory as follows: +Prior to executing `/cnb/lifecycle/analyzer`, you need to create a parent directory for this tutorial and two other directories inside it as follows: ```text +mkdir /tmp/tutorial # or your preferred directory +cd /tmp/tutorial mkdir -p apps/bash-script mkdir -p layers ``` @@ -283,7 +285,7 @@ Before running the `builder`, the following steps are required: cp -r apps/bash-script/* ./workspace ``` -3. Create a `launcher` file with instructions to run your application +3. Create a `launcher` file with instructions to run your application. Note that in a real buildpacks build, the `platform` does not create this file! The `samples/hello-moon` buildpack would create it. In our case, the `samples/hello-moon` buildpack hasn't been updated with this functionality, so we are faking that behavior. ```text mkdir -p layers/samples_hello-moon