New page "Basics of BuildPacks" under the Getting Started side menu #688
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,6 @@ | ||
| +++ | ||
| title="An App's Brief Journey from Source to Image" | ||
| weight=3 | ||
| getting-started=true | ||
| +++ | ||
|
|
||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,63 @@ | ||
| +++ | ||
| title="Basics of BuildPacks" | ||
| weight=2 | ||
| getting-started=true | ||
| +++ | ||
|
|
||
| ## Basic Concepts | ||
|
|
||
| ### What is a Buildpack? | ||
|
|
||
| A `buildpack` is software that transforms application source code into | ||
| executable files by analyzing the code and determining the best way to | ||
| build it. | ||
|
|
||
|  | ||
|
|
||
| ### What is a Builder? | ||
|
|
||
| A builder is an image that contains all the components necessary to | ||
| execute a build (for example, an ordered combination of buildpacks, a build | ||
| image and other files and configurations). | ||
|
|
||
|  | ||
|
|
||
| ### What is a Lifecycle? | ||
|
|
||
| A lifecycle is a series of steps that are used to create and manage a | ||
| buildpack. `create` is used to analyze, detect, restore, build, and export | ||
| buildpack execution. Next, `launcher` can be used to launch the application. | ||
| Finally, `rebase` can be used to push the latest changes to an existing | ||
| buildpack. All of these steps are part of a lifecycle. | ||
|
||
|
|
||
|  | ||
|
|
||
| ### What is a Platform | ||
|
|
||
| A platform typically refers to an organization or service provider (e.g., | ||
| kpack, Tekton, Fly.io, Digital Ocean, Google Cloud, Heroku, SalesForce, etc.) | ||
| that incorporates Buildpacks within their products to make buildpack | ||
| functionality available to their end-users (typically, application | ||
| developers). | ||
|
||
|
|
||
| A platform can be a: | ||
|
|
||
| - A local CLI tool | ||
| - A plugin for a continuous integration service | ||
| - A cloud application platform | ||
|
|
||
| ## Who uses Buildpacks (Personas) | ||
|
|
||
| ### App Developers | ||
|
|
||
| Regular Application developers that utilize Buildpacks in their app packaging | ||
| workflows. | ||
|
|
||
| ### Platform Operators | ||
|
|
||
| Operators of platforms (Google Cloud, Salesforce, etc.) that incorporate | ||
| Buildpacks within their platforms to simplify the end-user experience. | ||
|
|
||
| ### Buildpack Authors | ||
|
|
||
| Buildpacks' internal developers working on Buildpack features. | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've always found it difficult to describe what an individual buildpack is! A
buildpackis a small software component that does something. Would we be better off here to explain by example? i.e. provide an example of a "distribution" buildpack, an a "build process" buildpack?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Buildpacks have many shapes and forms. For example, a 'Distribution BuildPack' is a pre-built and tested buildpack that is ready for distribution to application developers. A Distribution Buildpack includes a set of buildpacks that are packaged together and can be used to build applications in different environments.
'Paketo Buildpacks' is a distribution buildpack for building applications in Java, Go, Python, Ruby, etc. The buildpacks included in 'Paketo Buildpacks' work together to create application container images that can run on any platform that supports container images (e.g., Cloud Foundry, Docker, Kubernetes, etc.).
Source: https://paketo.io/
P.s., I'm still connecting the dots with the core concepts, please see if the description is conceptually correct.