help

Signed-off-by: Doug Davis <[email protected]>

app-n-job/README.md

@@ -4,3 +4,13 @@ This will build an image that can be used for both Applications and Batch Jobs.
 By checking for the presence of the `JOB_INDEX` environment variable, the code
 will know whether to start a web service (Application) or just do its task
 and exit (Batch Job).
+
+- - -
+
+As noted in [the main README](../README.md), this sample has two pieces:
+
+- a `build` script which will build the container image used
+- a `run` script which deploys a new Application using that image
+
+The main purpose of this example is the `run` script, but the `build`
+script is included for complete educational (and reuse) purposes. 

app2job/README.md

@@ -9,3 +9,13 @@ The Application will wait for an HTTP PUT request containing the name of the
 Job definition in its HTTP Path. It will then use that Job definition name
 to submit a new Job. When the job is done, it will then check the logs of the
 Job to verify it worked correctly.
+
+- - -
+
+As noted in [the main README](../README.md), this sample has two pieces:
+
+- a `build` script which will build the container image used
+- a `run` script which deploys a new Application using that image
+
+The main purpose of this example is the `run` script, but the `build`
+script is included for complete educational (and reuse) purposes. 

bind-app/README.md

@@ -9,3 +9,13 @@ set of environment variables. But as the App owner you only need to look at
 the new environment variables that will be added to the App.
 
 In this sample we'll create an instance of a DB2 service.
+
+- - -
+
+As noted in [the main README](../README.md), this sample has two pieces:
+
+- a `build` script which will build the container image used
+- a `run` script which deploys a new Application using that image
+
+The main purpose of this example is the `run` script, but the `build`
+script is included for complete educational (and reuse) purposes. 

bind-job/README.md

@@ -8,3 +8,13 @@ your job. Meaning, it'll make the secret name/value pairs visible as a
 set of environment variables.
 
 In this sample we'll create an instance of a DB2 service.
+
+- - -
+
+As noted in [the main README](../README.md), this sample has two pieces:
+
+- a `build` script which will build the container image used
+- a `run` script which deploys a new Application using that image
+
+The main purpose of this example is the `run` script, but the `build`
+script is included for complete educational (and reuse) purposes. 

configmaps/README.md

@@ -9,3 +9,13 @@ environment variable.
 The application will log (print to stdout) all of its environment variables.
 
 Note: the same basic logic will work for Batch Jobs as well.
+
+- - -
+
+As noted in [the main README](../README.md), this sample has two pieces:
+
+- a `build` script which will build the container image used
+- a `run` script which deploys a new Application using that image
+
+The main purpose of this example is the `run` script, but the `build`
+script is included for complete educational (and reuse) purposes. 

cos-event/README.md

@@ -22,3 +22,13 @@ CRN/ID (the value in the first column of each row). If you leave this
 variable unset, the `run` script will attempt to create a `lite` (free of
 charge) COS instance for you, which it will then delete upon completion. It
 will not delete any existing instance you specify via the `COS_ID` variable.
+
+- - -
+
+As noted in [the main README](../README.md), this sample has two pieces:
+
+- a `build` script which will build the container image used
+- a `run` script which deploys a new Application using that image
+
+The main purpose of this example is the `run` script, but the `build`
+script is included for complete educational (and reuse) purposes. 

hello/README.md

@@ -1,3 +1,13 @@
 # Hello
 
 A pretty simple node.js application. Gotta start some place.
+
+- - -
+
+As noted in [the main README](../README.md), this sample has two pieces:
+
+- a `build` script which will build the container image used
+- a `run` script which deploys a new Application using that image
+
+The main purpose of this example is the `run` script, but the `build`
+script is included for complete educational (and reuse) purposes. 

helloworld/README.md

@@ -6,3 +6,13 @@ return "Hello World" back to the caller.
 Check the source code for all of the things you can make it do either via
 environment variables or query parameters. This is good for testing the
 system to see how it reacts - for example, when the app crashes.
+
+- - -
+
+As noted in [the main README](../README.md), this sample has two pieces:
+
+- a `build` script which will build the container image used
+- a `run` script which deploys a new Application using that image
+
+The main purpose of this example is the `run` script, but the `build`
+script is included for complete educational (and reuse) purposes. 

job/README.md

@@ -9,3 +9,13 @@ This sample shows up to run a batch job. It will create the batch job two ways:
 Each instance of each Job submitted will print, to its logs, its "index",
 which is defined by its `JOB_INDEX` environment variable. The `run` script
 will print some of the log files to show this.
+
+- - -
+
+As noted in [the main README](../README.md), this sample has two pieces:
+
+- a `build` script which will build the container image used
+- a `run` script which deploys a new Application using that image
+
+The main purpose of this example is the `run` script, but the `build`
+script is included for complete educational (and reuse) purposes. 

job2app/README.md

@@ -10,3 +10,13 @@ When the Job is run, each instance will call the App 10 times. Which means
 by setting the `array-indices` to a range of 50, the App should be hit 500
 times. At the end of `run` it will ask the App for the number of times it
 was called, to verify the count.
+
+- - -
+
+As noted in [the main README](../README.md), this sample has two pieces:
+
+- a `build` script which will build the container image used
+- a `run` script which deploys a new Application using that image
+
+The main purpose of this example is the `run` script, but the `build`
+script is included for complete educational (and reuse) purposes. 

ping/README.md

@@ -7,3 +7,13 @@ minute and will contain just a simple JSON object as the payload.
 The App will log (print to stdout) each event as it arrives, showing the
 full set of HTTP Headers and HTTP Body payload. This makes it a useful
 tool for testing other Event Sources, to see what they generate.
+
+- - -
+
+As noted in [the main README](../README.md), this sample has two pieces:
+
+- a `build` script which will build the container image used
+- a `run` script which deploys a new Application using that image
+
+The main purpose of this example is the `run` script, but the `build`
+script is included for complete educational (and reuse) purposes. 

secrets/README.md

@@ -12,3 +12,13 @@ environment variable.
 The application will log (print to stdout) all of its environment variables.
 
 Note: the same basic logic will work for Batch Jobs as well.
+
+- - -
+
+As noted in [the main README](../README.md), this sample has two pieces:
+
+- a `build` script which will build the container image used
+- a `run` script which deploys a new Application using that image
+
+The main purpose of this example is the `run` script, but the `build`
+script is included for complete educational (and reuse) purposes. 

sessions/README.md

@@ -16,3 +16,13 @@ expand this to store/share state across multiple instances of the app.
 When run, you should see each `curl` return the `Counter` value.
 The order might not be perfect due to timing issues, but as long as you don't
 see duplicates and the final `curl` returns `100` then it worked.
+
+- - -
+
+As noted in [the main README](../README.md), this sample has two pieces:
+
+- a `build` script which will build the container image used
+- a `run` script which deploys a new Application using that image
+
+The main purpose of this example is the `run` script, but the `build`
+script is included for complete educational (and reuse) purposes.