From 493d9fea97a6dff7aa7da18ac1dcfac0c4785017 Mon Sep 17 00:00:00 2001 From: Matti Tahvonen Date: Thu, 21 Aug 2025 14:43:56 +0300 Subject: [PATCH] Update configuration.html.markerb MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Changed to a builder that is still maintained. Not sure if the separate buildpacks parameter is needed, but kept that as as separate examp.e Also note, I wonder why you don't fall back to buildpacks if Dockerfile does not exist🤷‍♂️ At least it could do a priming build if it succeeds and if so, then drop this line to the tly.toml. --- reference/configuration.html.markerb | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/reference/configuration.html.markerb b/reference/configuration.html.markerb index 36f2886f6f..04a7a31156 100644 --- a/reference/configuration.html.markerb +++ b/reference/configuration.html.markerb @@ -98,13 +98,19 @@ The optional build section contains key/values concerned with how the applicatio ```toml [build] - builder = "paketobuildpacks/builder:base" - buildpacks = ["gcr.io/paketo-buildpacks/nodejs"] + builder = "paketobuildpacks/builder-jammy-base" ``` The builder "builder" uses CNB Buildpacks and Builders to create the application image. These are third party toolkits which can use Heroku compatible build processes or other tools. The tooling is all managed by the buildpacks and buildpacks are assembled into CNB Builders - images complete with the buildpacks and OS to run the tool chains. -In our example above, the builder is being set to use [Paketo's all-purpose builder](https://paketo.io) with the NodeJS buildpack. +In our example above, the builder is being set to use [Paketo's all-purpose builder](https://paketo.io) which automatically detects needed buildpacks. + +You can also explicitly define buildpacks: +```toml +[build] + builder = "paketobuildpacks/builder:base" + buildpacks = ["gcr.io/paketo-buildpacks/nodejs"] +``` ### Specify a Docker image