Try to fix ugo

Signed-off-by: Natalie Arellano <[email protected]>

Author: Natalie Arellano

content/docs/extension-author-guide/create-extension/build-dockerfile.md

@@ -11,7 +11,7 @@ weight=404
 
 <!-- test:exec -->
 ```bash
-cat $workspace/samples/extensions/tree/bin/detect
+cat $PWD/samples/extensions/tree/bin/detect
 ```
 
 The extension always detects (because its exit code is `0`) and provides a dependency called `tree` by writing to the build plan.
@@ -20,26 +20,26 @@ The extension always detects (because its exit code is `0`) and provides a depen
 
 <!-- test:exec -->
 ```bash
-cat $workspace/samples/extensions/tree/bin/generate
+cat $PWD/samples/extensions/tree/bin/generate
 ```
 
 The extension generates a `build.Dockerfile` that installs `tree` on the builder image.
 
 ### Re-create our builder with `hello-extensions` updated to require `tree`
 
-Edit `$workspace/samples/buildpacks/hello-extensions/bin/detect` to uncomment the first set of lines that output `[[requires]]` to the build plan:
+Edit `$PWD/samples/buildpacks/hello-extensions/bin/detect` to uncomment the first set of lines that output `[[requires]]` to the build plan:
 
 <!-- test:exec -->
 ```bash
-sed -i '' "10,11s/#//" $workspace/samples/buildpacks/hello-extensions/bin/detect
+sed -i "10,11s/#//" $PWD/samples/buildpacks/hello-extensions/bin/detect
 ```
 
 Re-create the builder:
 
 <!-- test:exec -->
 ```
-pack builder create $registry_namespace/extensions-builder \
-  --config $workspace/samples/builders/alpine/builder.toml \
+pack builder create localhost:5000/extensions-builder \
+  --config $PWD/samples/builders/alpine/builder.toml \
   --publish
 ```
 
@@ -48,13 +48,14 @@ pack builder create $registry_namespace/extensions-builder \
 <!-- test:exec -->
 ```
 pack build hello-extensions \
-  --builder $registry_namespace/extensions-builder \
+  --builder localhost:5000/extensions-builder \
   --network host \
-  --path $workspace/samples/apps/java-maven \
+  --path $PWD/samples/apps/java-maven \
+  --pull-policy always \
   --verbose
 ```
 
-Note that `--network host` is necessary when using `registry_namespace=localhost:5000`.
+Note that `--network host` is necessary when publishing to a local registry.
 
 You should see:
 

content/docs/extension-author-guide/create-extension/building-blocks-extension.md

@@ -9,7 +9,7 @@ weight=403
 
 <!-- test:exec -->
 ```bash
-tree $workspace/samples/extensions/tree
+tree $PWD/samples/extensions/tree
 ```
 
 (That's right, we're using the very tool we will later be installing!) You should see something akin to the following:

content/docs/extension-author-guide/create-extension/run-dockerfile.md

@@ -11,7 +11,7 @@ weight=405
 
 <!-- test:exec -->
 ```bash
-cat $workspace/samples/extensions/curl/bin/detect
+cat $PWD/samples/extensions/curl/bin/detect
 ```
 
 The extension always detects (because its exit code is `0`) and provides a dependency called `curl`.
@@ -20,7 +20,7 @@ The extension always detects (because its exit code is `0`) and provides a depen
 
 <!-- test:exec -->
 ```bash
-cat $workspace/samples/extensions/curl/bin/generate
+cat $PWD/samples/extensions/curl/bin/generate
 ```
 
 The extension generates a `run.Dockerfile` that switches the run image to reference `run-image-curl`.
@@ -29,7 +29,7 @@ The extension generates a `run.Dockerfile` that switches the run image to refere
 
 <!-- test:exec -->
 ```bash
-cat $workspace/samples/stacks/alpine/run/curl.Dockerfile
+cat $PWD/samples/stacks/alpine/run/curl.Dockerfile
 ```
 
 This is a simple Dockerfile that creates a CNB run image from the `curl` base image by adding the required CNB user configuration and `io.buildpacks.stack.id` label.
@@ -41,25 +41,25 @@ Build the run image:
 <!-- test:exec -->
 ```bash
 docker build \
-  --file $workspace/samples/stacks/alpine/run/curl.Dockerfile \
+  --file $PWD/samples/stacks/alpine/run/curl.Dockerfile \
   --tag run-image-curl .
 ```
 
 ### Re-create our builder with `hello-extensions` updated to require `curl`
 
-Edit `$workspace/samples/buildpacks/hello-extensions/bin/detect` to uncomment the second set of lines that output `[[requires]]` to the build plan:
+Edit `$PWD/samples/buildpacks/hello-extensions/bin/detect` to uncomment the second set of lines that output `[[requires]]` to the build plan:
 
 <!-- test:exec -->
 ```bash
-sed -i '' "14,15s/#//" $workspace/samples/buildpacks/hello-extensions/bin/detect
+sed -i "14,15s/#//" $PWD/samples/buildpacks/hello-extensions/bin/detect
 ```
 
 Re-create the builder:
 
 <!-- test:exec -->
 ```bash
-pack builder create $registry_namespace/extensions-builder \
-  --config $workspace/samples/builders/alpine/builder.toml \
+pack builder create localhost:5000/extensions-builder \
+  --config $PWD/samples/builders/alpine/builder.toml \
   --publish
 ```
 
@@ -68,13 +68,14 @@ pack builder create $registry_namespace/extensions-builder \
 <!-- test:exec -->
 ```bash
 pack build hello-extensions \
-  --builder $registry_namespace/extensions-builder \
-  --path $workspace/samples/apps/java-maven \
+  --builder localhost:5000/extensions-builder \
+  --path $PWD/samples/apps/java-maven \
+  --pull-policy always \
   --network host \
   --verbose
 ```
 
-Note that `--network host` is necessary when using `registry_namespace=localhost:5000`.
+Note that `--network host` is necessary when publishing to a local registry.
 
 You should see:
 

content/docs/extension-author-guide/create-extension/setup-local-environment.md

@@ -41,9 +41,8 @@ Server: Docker Engine - Community
 
 ### Setup workspace directory
 
-<!-- test:exec -->
 ```bash
-workspace=$PWD # or your preferred workspace directory
+cd <your preferred workspace directory>
 ```
 
 ### Ensure pack version supports image extensions
@@ -66,9 +65,7 @@ pack config experimental true
 
 <!-- test:exec -->
 ```bash
-cd $workspace
 git clone https://github.com/buildpacks/samples.git
-cd samples
 ```
 
 <!--+ if false +-->

content/docs/extension-author-guide/create-extension/why-dockerfiles.md

@@ -13,7 +13,7 @@ Let's see a build that requires base image extension in order to succeed.
 
 <!-- test:exec -->
 ```bash
-cat $workspace/samples/buildpacks/hello-extensions/bin/detect
+cat $PWD/samples/buildpacks/hello-extensions/bin/detect
 ```
 
 The buildpack always detects (because its exit code is `0`) but doesn't require any dependencies (as the output build plan is empty).
@@ -22,7 +22,7 @@ The buildpack always detects (because its exit code is `0`) but doesn't require
 
 <!-- test:exec -->
 ```bash
-cat $workspace/samples/buildpacks/hello-extensions/bin/build
+cat $PWD/samples/buildpacks/hello-extensions/bin/build
 ```
 
 The buildpack tries to use `tree` at build-time, and defines a launch process called `curl` that runs `curl --version` at runtime.
@@ -52,8 +52,8 @@ Create the builder:
 
 <!-- test:exec -->
 ```bash
-pack builder create $registry_namespace/extensions-builder \
-  --config $workspace/samples/builders/alpine/builder.toml \
+pack builder create localhost:5000/extensions-builder \
+  --config $PWD/samples/builders/alpine/builder.toml \
   --publish
 ```
 
@@ -63,14 +63,14 @@ Run `pack build` (note that the "source" directory is effectively ignored in our
 
 ```
 pack build hello-extensions \
-  --builder $registry_namespace/extensions-builder \
+  --builder localhost:5000/extensions-builder \
   --network host \
-  --path $workspace/samples/apps/java-maven \
+  --path $PWD/samples/apps/java-maven \
   --pull-policy always \
   --verbose
 ```
 
-Note that `--network host` is necessary when using `registry_namespace=localhost:5000`.
+Note that `--network host` is necessary when publishing to a local registry.
 
 You should see: