Skip to content

Commit 3190e73

Browse files
author
Natalie Arellano
committed
Split buildpack author guide (except tutorial) into concepts and how-to
Signed-off-by: Natalie Arellano <[email protected]>
1 parent 24f1cb3 commit 3190e73

File tree

8 files changed

+16
-7
lines changed

8 files changed

+16
-7
lines changed

content/docs/buildpack-author-guide/caching-strategies.md renamed to content/docs/for-buildpack-authors/concepts/caching-strategies.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
+++
2-
title="Layer Types"
3-
weight=6
4-
summary="Learn strategies for caching layers."
2+
title="Caching strategies"
3+
weight=1
4+
summary="Learn strategies for caching layers at build-time for future re-use."
55
+++
66

77
# Layers

content/docs/buildpack-author-guide/build-phases-overview.md renamed to content/docs/for-buildpack-authors/concepts/lifecycle-phases.md

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,15 @@
11
+++
2-
title="Overview of Buildpacks Phases"
3-
weight=15
2+
title="Lifecycle phases"
3+
weight=2
44
+++
55

6-
We work through a full example of building a "hello world" NodeJs web application. In the example we run `pack` on the NodeJS application to produce an application image. We assume that we have a NodeJS buildpack, `registry.fake/buildpacks/nodejs:latest`, that is decomposed into buildpacks that help with the build. We expand each of the buildpacks phases to explain the process. Throughout the example we take a production-level view of their operation. For example, our assumed NodeJS buildpack will be described to create different build, cache and launch layers in a manner similar to how a real NodeJS buildpack would operate.
6+
There are five phases to a buildpacks build.
7+
8+
<!--more-->
9+
10+
We work through a full example of building a "hello world" NodeJs web application.
11+
12+
In the example we run `pack` on the NodeJS application to produce an application image. We assume that we have a NodeJS buildpack, `registry.fake/buildpacks/nodejs:latest`, that is decomposed into buildpacks that help with the build. We expand each of the buildpacks phases to explain the process. Throughout the example we take a production-level view of their operation. For example, our assumed NodeJS buildpack will be described to create different build, cache and launch layers in a manner similar to how a real NodeJS buildpack would operate.
713

814
## NodeJS buildpack
915

File renamed without changes.

content/docs/for-platform-operators/concepts/dockerfiles.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,11 @@
11
+++
22
title="Dockerfiles"
3-
summary="Dockerfiles can be used to extend base images for buildpacks builds."
43
+++
54

5+
Dockerfiles can be used to extend base images for buildpacks builds.
6+
7+
<!--more-->
8+
69
## Why Dockerfiles?
710

811
Buildpacks can do a lot, but there are some things buildpacks can't do. They can't install operating system packages,

0 commit comments

Comments
 (0)