Skip to content

Commit f16039a

Browse files
author
Doug Davis
committed
tweaks
Signed-off-by: Doug Davis <[email protected]>
1 parent cd2ab6e commit f16039a

File tree

5 files changed

+32
-25
lines changed

5 files changed

+32
-25
lines changed

README.md

+4
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,10 @@ $ ic ce project create --name demos --target
4242
- [job](job)<br>
4343
This will demostrate how to create a simple Batch Job and how to have it
4444
communicate with an Application running within the same project.
45+
- [s2i-buildpacks](s2i-buildpacks)<br>
46+
This will show how to use the source-to-image feature of Code Engine to
47+
build an app from a git repo (using a Buildpack), push it to a private
48+
registry, and then deploy an app using that image.
4549
- [s2i-dockerfile](s2i-dockerfile)<br>
4650
This will show how to use the source-to-image feature of Code Engine to
4751
build an app from a git repo (using a Dockerfile), push it to a private

s2i-buildpacks/README.md

+12-11
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,17 @@
1-
# Code Engine Source-to-Image Buildpacks support
1+
# Source-to-Image with Buildpacks
22

3-
This sample shows how to use the Code Engine source-to-image Buildpacks feature
4-
to build your application from a git repo, push the image into a registry,
5-
and then deploy it as a Code Engine application. It doesn't require a Dockerfile in the git repo.
3+
This sample shows how to use the Code Engine source-to-image feature using
4+
Buildpacks to build your application from a git repo, push the image into a
5+
registry, and then deploy it as a Code Engine application. It doesn't require
6+
a Dockerfile in the git repo.
67

7-
More details and supported runtimes and versions can be found in [Code Engine Docs](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-build).
8+
More details and supported runtimes and versions can be found in [Code Engine
9+
Docs](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-build).
810

911
The exact steps taken in [`run`](./run) are:
10-
- Login and create an ICR (IBM Container Registry) namespace to store the resulting
11-
image
12-
- Create an IBM API Key that will be used by the build process to push
13-
the image to ICR
14-
- Define a build that points to a git repo for the source, and the
15-
defines where in ICR to store the image
12+
- Create an ICR (IBM Container Registry) namespace to store the resulting image
13+
- Create an IBM API Key that will be used by the build process to push the
14+
image to ICR
15+
- Define a build that points to a git repo for the source, and then defines
16+
where in ICR to store the image
1617
- Creates a Code Engine app from that image

s2i-buildpacks/run

+2-1
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,8 @@ ic iam api-key-create s2i-sample | \
3131

3232
# Define the build of this dir in this github repo
3333
ic ce build create -n mybuild -i "us.icr.io/${ICR_NS}/app" --rs icr \
34-
--source https://github.com/IBM/CodeEngine --context-dir s2i-buildpacks --strategy buildpacks
34+
--source https://github.com/IBM/CodeEngine --context-dir s2i-buildpacks \
35+
--strategy buildpacks
3536

3637
# Now kick off the build itself
3738
ic ce buildrun submit -n myrun --build mybuild

s2i-dockerfile/README.md

+13-12
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,18 @@
1-
# Code Engine Source-to-Image Dockerfile support
1+
# Source-to-Image with a Dockerfile
22

3-
This sample shows how to use the Code Engine source-to-image Dockerfile feature
4-
to build your application from a git repo, push the image into a registry,
5-
and then deploy it as a Code Engine application. This will assume that there's
6-
a Dockerfile in the root of the git repo that will be used to build the image.
3+
This sample shows how to use the Code Engine source-to-image feature using
4+
a Dockerfile to build your application from a git repo, push the image into a
5+
registry, and then deploy it as a Code Engine application. This will assume
6+
that there's a Dockerfile in the root of the build context that will be used
7+
to build the image.
78

8-
More details can be found in [Code Engine Docs](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-build).
9+
More details can be found in [Code Engine
10+
Docs](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-build).
911

1012
The exact steps taken in [`run`](./run) are:
11-
- Login and create an ICR (IBM Container Registry) namespace to store the resulting
12-
image
13-
- Create an IBM API Key that will be used by the build process to push
14-
the image to ICR
15-
- Define a build that points to a git repo for the source, and the
16-
defines where in ICR to store the image
13+
- Create an ICR (IBM Container Registry) namespace to store the resulting image
14+
- Create an IBM API Key that will be used by the build process to push the
15+
image to ICR
16+
- Define a build that points to a git repo for the source, and then define
17+
where in ICR to store the image
1718
- Creates a Code Engine app from that image

s2i-dockerfile/app.go

+1-1
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ import (
66
)
77

88
func Handler(w http.ResponseWriter, r *http.Request) {
9-
fmt.Fprintf(w, "\n\nI was built by Dockerfile with Code Engine!\n\n\n")
9+
fmt.Fprintf(w, "\n\nI was built with a Dockerfile by Code Engine!\n\n\n")
1010
}
1111

1212
func main() {

0 commit comments

Comments
 (0)