paketo-buildpacks / samples

A collection of samples

Paketo Buildpacks Sample Applications

A collection of sample applications that can be built using Paketo Buildpacks.

Prerequisites

1. Clone this repository: git clone https://github.com/paketo-buildpacks/samples
2. Pack

Adding New Samples

• If the app is a part of an existing language family:
  • Add app to the appropriate language family in its own subdirectory.
  • Add a test context to the *_test.go file in the language family directory.
• If the app is a part of a new language family:
  • Create a new directory for the language family.
  • Create a new test file <language_family_name>/*_test.go containing a new test suite.
  • Be mindful of which builders the app is compatible with and set up test suites accordingly.
  • Run ./scripts/generate-test-workflow.sh -l <language_family_name> to generate a Github Actions workflow that runs the tests.
• Update README.md.

Samples

Java

• AspectJ
• Azure Application Insights
• Gradle DistZip
• Gradle
• Kotlin
• Leiningen (Clojure)
• Maven
• Native Image
• OpenTelemetry
• Pre-compiled JAR
• Scala Akka
• WAR

Node.js

• No Package Manager
• NPM
• Yarn

Dotnet Core

• Runtime-only
• ASPNet

Go

• No Imports
• Mod

PHP

• Built-in Webserver
• NGINX
• Apache HTTPD
• Composer
• Composer with Extensions
• Extensions via custon .ini
• Memcached Session Handler
• Redis Session Handler

Ruby

• Passenger
• Puma
• Rackup
• Rake
• Thin
• Unicorn

Python

• No Package Manager
• Pip
• Pipenv
• Miniconda
• Poetry (dependency management only)
• Poetry (dependency management and run commands)

Procfile

• Static Webserver

Web Servers

• HTTPD
• NGINX
• Zero Configuration
• JavaScript Frontend

Testing Samples

To run integration tests that pack build each of the sample apps, use scripts/smoke.sh. See scripts/smoke.sh -h for usage information.

For example, to run tests for the Go and .NET Core samples with the Paketo tiny and base builders, run:

./smoke.sh --builder paketobuildpacks/builder-jammy-tiny:latest \
           --builder paketobuildpacks/builder-jammy-base:latest \
           --suite go \
           --suite dotnet-core

samples's Issues

Add Rails sample

Now that we have a Rails assets buildpack could we add a Rails sample app? It can probably use any webserver.

Failure: 'Test All Samples' workflow

Test php workflow failed. Please take a look to ensure samples are working. (cc @paketo-buildpacks/content-maintainers)

Procfile sample seems broken

When I build and deploy the Procfile sample, I get the error:

$ kubectl logs procfile-bdcxb-1-deployment-79657fc75f-nf9vb user-container
FOLDER=web: FOLDER=web: command not found

I believe this likely comes from here:

samples/procfile/Procfile

Line 1 in d82d470

web: FOLDER=web ./static-file-server-1.8.0-linux-amd64

It sort of seems like the sample it treating the first argument as the binary executable instead of an environment variable to pass to the binary executable (as a shell might).

Smoke tests not run on PR

What happened?

After PR was submitted, smoke tests were not run as a github action

• What were you attempting to do?

• What did you expect to happen?

• What was the actual behavior? Please provide log output, if possible.

Build Configuration

• What platform (pack, kpack, tekton buildpacks plugin, etc.) are you
  using? Please include a version.

• What buildpacks are you using? Please include versions.

• What builder are you using? If custom, can you provide the output from pack inspect-builder <builder>?

• Can you provide a sample app or relevant configuration (buildpack.yml,
  nginx.conf, etc.)?

Checklist

• I have included log output.
• The log output includes an error message.
• I have included steps for reproduction.

Add Jammy+Python to integration tests

Add Jammy+Python to integration tests

Maybe blocked on:

• paketo-buildpacks/builder-jammy-full#13
• paketo-buildpacks/builder-jammy-base#23

Failure: 'Test All Samples' workflow

Test ruby workflow failed. Please take a look to ensure samples are working. (cc @paketo-buildpacks/content-maintainers)

Failure: 'Test All Samples' workflow

Test web-servers workflow failed. Please take a look to ensure samples are working. (cc @paketo-buildpacks/content-maintainers)

Unable to derive a gradle based version of the public-static-main native-image maven sample

I started from the public-static-main sample, removed the maven project file, and used instead:

build.gradle.kts

plugins {
    `java-library`
}

tasks.jar {
    manifest {
        attributes["Main-Class"] = "io.paketo.App"
    }
}

gradle-wrapper.properties

distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-7.4.1-bin.zip
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists

Pack command + Output

$ pack build --builder paketobuildpacks/builder:tiny --env BP_NATIVE_IMAGE=true public-static-main:gradle
...
Downloading from https://download.bell-sw.com/vm/22.0.0.2/bellsoft-liberica-vm-core-openjdk11-22.0.0.2-linux-amd64.tar.gz
...
Downloading https://services.gradle.org/distributions/gradle-7.4.1-bin.zip
...
Daemon will be stopped at the end of the build 
      > Task :compileJava
      > Task :processResources NO-SOURCE
      > Task :classes
      > Task :jar
      > Task :assemble
      
      BUILD SUCCESSFUL in 36s
      2 actionable tasks: 2 executed
...
Paketo Native Image Buildpack 5.2.0
  https://github.com/paketo-buildpacks/native-image
  Build Configuration:
    $BP_BINARY_COMPRESSION_METHOD                Compression mechanism used to reduce binary size. Options: `none` (default), `upx` or `gzexe`
    $BP_NATIVE_IMAGE                       true  enable native image build
    $BP_NATIVE_IMAGE_BUILD_ARGUMENTS             arguments to pass to the native-image command
    $BP_NATIVE_IMAGE_BUILD_ARGUMENTS_FILE        a file with arguments to pass to the native-image command
    $BP_NATIVE_IMAGE_BUILT_ARTIFACT              the built application artifact explicitly, required if building from a JAR
  Native Image: Contributing to layer
    GraalVM 22.0.0.2 Java 11 CE (Java Version 11.0.14.1+1-LTS)
    Executing native-image -H:+StaticExecutableWithDynamicLibC -jar /workspace
Error: /workspace is a directory. (-jar requires a valid jarfile)
unable to invoke layer creator
unable to contribute native-image layer
error running build
exit status 1
ERROR: failed to build: exit status 1
ERROR: failed to build: executing lifecycle: failed with status code: 51

There's too much magic going on, and I have absolutely no idea whether I'm doing something wrong, or whether what I'm trying to do is unsupported.

Can you provide a working example for native-image + gradle?

Failure: 'Test All Samples' workflow

Test nginx workflow failed. Please take a look to ensure samples are working. (cc @paketo-buildpacks/content-maintainers)

Unable to run example from documentation, GCR auth

What happened?

gcr.io wouldn't let me download the image needed

• What were you attempting to do?
  • Use the sample, as described and copy/pasta'd from docs

git clone https://github.com/paketo-buildpacks/samples
cd samples/dotnet-core/aspnet
pack build my-app --buildpack gcr.io/paketo-buildpacks/dotnet-core \
  --builder paketobuildpacks/builder:base

• What did you expect to happen?
  • To be able to build the sample project.
• What was the actual behavior? Please provide log output, if possible.
  • auth for ref gcr.io/paketo-buildpacks/dotnet-core failed

git clone https://github.com/paketo-buildpacks/samples
cd samples/dotnet-core/aspnet
pack build my-app --buildpack gcr.io/paketo-buildpacks/dotnet-core \
  --builder paketobuildpacks/builder:base

Cloning into 'samples'...
remote: Enumerating objects: 1783, done.
remote: Counting objects: 100% (483/483), done.
remote: Compressing objects: 100% (242/242), done.
remote: Total 1783 (delta 345), reused 332 (delta 231), pack-reused 1300
Receiving objects: 100% (1783/1783), 22.78 MiB | 512.00 KiB/s, done.
Resolving deltas: 100% (971/971), done.
base: Pulling from paketobuildpacks/builder
Digest: sha256:8f82384b8c6ec0415c5b62df6fbc4f28e52154a6f084af851fa3a8b0fd726fba
Status: Image is up to date for paketobuildpacks/builder:base
base-cnb: Pulling from paketobuildpacks/run
Digest: sha256:3bdefd40188e93e4aba93978440816f9b86d03a1a7b58e6c6c854bcb88df8ace
Status: Image is up to date for paketobuildpacks/run:base-cnb
ERROR: failed to build: creating from buildpackage gcr.io/paketo-buildpacks/dotnet-core: fetching image: resolve auth for ref gcr.io/paketo-buildpacks/dotnet-core: error getting credentials - err: exec: "docker-credential-gcloud": executable file not found in $PATH, out: ``

Build Configuration

• What platform (pack, kpack, tekton buildpacks plugin, etc.) are you
  using? Please include a version.
  • pack --version => 0.20.0+git-66a4f32.build-2668
• What buildpacks are you using? Please include versions.
  • Sorry, I'm not sure. Whatever the sample would get?
• What builder are you using? If custom, can you provide the output from pack inspect-builder <builder>?
  • Huge output, I can post this to a gist if needed.
• Can you provide a sample app or relevant configuration (buildpack.yml,
  nginx.conf, etc.)?
  • Sorry, also not sure here. Just used the sample.

Checklist

• I have included log output.
• The log output includes an error message.
• I have included steps for reproduction.

Other

I really hope I didn't miss some step in the docs, but please let me know if I did.

Add a smoke test for ca-certificates sample app

What happened?

Issue #47 is to implement tests for all of the sample apps against our builders. The test case for the ca-certificates sample app is less straightforward than the other test cases.

After discussing with @ekcasey, this will involve the following:

• generating a CA cert
• generating a cert signed by the CA
• standing up some kind of server that uses the above cert (during manual testing a used the nginx docker image for this)
• passing the endpoint of the server to the buildpack (at both build and run time)

We are punting this work from the initial testing issue, and into its own chunk of work. We would like to have this tested eventually.

Checklist

• I have included log output.
• The log output includes an error message.
• I have included steps for reproduction.

Create HTTPD stand-alone sample app

HTTPD is a stand-alone buildpack in the Paketo Full builder. We should have a sample app to demonstrate the stand-alone use of the buildpack.

Failure: 'Test All Samples' workflow

Test java workflow failed. Please take a look to ensure samples are working. (cc @paketo-buildpacks/content-maintainers)

Add a sample app that builds static assets with npm and then serves them

What happened?

• What were you attempting to do?

Use the nodejs buildpack to build and then serve some static assets. My Dockerfile uses

RUN npm run build:app:docker

to build the static assets.

• What did you expect to happen?

I expected to find an example of how to do this with buildpacks because it's a common pattern for React frontend apps.

• What was the actual behavior? Please provide log output, if possible.

There isn't an example!

Checklist

• I have included log output.
• The log output includes an error message.
• I have included steps for reproduction.

Replace buildpack.yml examples with environment variables

What happened?

There are several sample apps in this repo that still reference the buildpack.yml format for configuration. We should update all of these apps to use environment variables either through the addition of a project.toml or updating the pack build commands in the README to explicitly set this environment variable.

Seemingly unnecessary references to cloudfoundry

samples/nginx/nginx-sample/nginx.conf

Lines 9 to 10 in 1ef971f

	log_format cloudfoundry 'NginxLog "$request" $status $body_bytes_sent';
	access_log /dev/stdout cloudfoundry;

Add sample app that uses a procfile

Could we add a sample in here that provides a reference of how to use the Procfile buildpack to set the app image start command?

Add Yarn Berry apps to Node.js samples

Once support for building Yarn Berry applications has been added to the Node.js buildpack (RFC 0014), the Yarn samples should be updated to include examples of those use cases.

Failure: 'Test All Samples' workflow

Test dotnet-core workflow failed. Please take a look to ensure samples are working. (cc @paketo-buildpacks/content-maintainers)

All buildpack registry references should be updated from GCR to Dockerhub

What happened?

We've recently started publishing all Paketo Buildpac artifacts to Dockerhub in addition to GCR. We should update all existing documentation to reference the Dockerhub locations so that we can eventually move over to Dockerhub completely.

Running "Getting Started" gives node dependancy error

What happened?

• What were you attempting to do?
  Perform the "Getting Started" steps

• What did you expect to happen?
  No errors, sample app built

• What was the actual behavior? Please provide log output, if possible.

Paketo CA Certificates Buildpack 2.2.0
  https://github.com/paketo-buildpacks/ca-certificates
  Launch Helper: Contributing to layer
    Creating /layers/paketo-buildpacks_ca-certificates/helper/exec.d/ca-certificates-helper
Paketo Node Engine Buildpack 0.4.0
  Resolving Node Engine version
    Candidate version sources (in priority order):
      package.json -> "~10"
      <unknown>    -> ""

failed to satisfy "node" dependency version constraint "~10": no compatible versions. Supported versions are: [12.22.0, 12.22.1, 14.16.1, 14.17.0, 15.13.0, 15.14.0, 16.1.0, 16.2.0]
ERROR: failed to build: exit status 1
ERROR: failed to build: executing lifecycle: failed with status code: 145

Build Configuration

• What platform (pack, kpack, tekton buildpacks plugin, etc.) are you
  using? Please include a version.

• What buildpacks are you using? Please include versions.
  Fresh install of pack using brew install buildpacks/tap/pack

➜  ~ pack --version
0.19.0+git-360dbae.build-2550

• What builder are you using? If custom, can you provide the output from pack inspect-builder <builder>?
• Can you provide a sample app or relevant configuration (buildpack.yml,
  nginx.conf, etc.)?

Performed steps noted here:
https://paketo.io/docs/

Checklist

• I have included log output.
• The log output includes an error message.
• I have included steps for reproduction.

Failure: 'Test All Samples' workflow

Test java workflow failed. Please take a look to ensure samples are working. (cc @paketo-buildpacks/content-maintainers)

akka sample failing

This morning I saw a string of failures in the akka sample with:

  [build] [error] sbt.librarymanagement.ResolveException: Error downloading com.typesafe.sbt:sbt-native-packager;sbtVersion=1.0;scalaVersion=2.12:1.7.5
  [build] [error]   Not found
  [build] [error]   Not found
  [build] [error]   not found: https://repo1.maven.org/maven2/com/typesafe/sbt/sbt-native-packager_2.12_1.0/1.7.5/sbt-native-packager-1.7.5.pom
  [build] [error]   not found: /home/cnb/.ivy2/local/com.typesafe.sbt/sbt-native-packager/scala_2.12/sbt_1.0/1.7.5/ivys/ivy.xml
  [build] [error]   download error: Caught java.net.UnknownHostException: repo.scala-sbt.org (repo.scala-sbt.org) while downloading https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/com.typesafe.sbt/sbt-native-packager/scala_2.12/sbt_1.0/1.7.5/ivys/ivy.xml
  [build] [error]   not found: https://repo.typesafe.com/typesafe/ivy-releases/com.typesafe.sbt/sbt-native-packager/scala_2.12/sbt_1.0/1.7.5/ivys/ivy.xml
  [build] [error] Error downloading io.spray:sbt-revolver;sbtVersion=1.0;scalaVersion=2.12:0.9.1
  [build] [error]   Not found
  [build] [error]   Not found
  [build] [error]   not found: https://repo1.maven.org/maven2/io/spray/sbt-revolver_2.12_1.0/0.9.1/sbt-revolver-0.9.1.pom
  [build] [error]   not found: /home/cnb/.ivy2/local/io.spray/sbt-revolver/scala_2.12/sbt_1.0/0.9.1/ivys/ivy.xml
  [build] [error]   download error: Caught java.net.UnknownHostException: repo.scala-sbt.org (repo.scala-sbt.org) while downloading https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/io.spray/sbt-revolver/scala_2.12/sbt_1.0/0.9.1/ivys/ivy.xml
  [build] [error]   not found: https://repo.typesafe.com/typesafe/ivy-releases/io.spray/sbt-revolver/scala_2.12/sbt_1.0/0.9.1/ivys/ivy.xml
  [build] [error] 	at lmcoursier.CoursierDependencyResolution.unresolvedWarningOrThrow(CoursierDependencyResolution.scala:249)
  [build] [error] 	at lmcoursier.CoursierDependencyResolution.$anonfun$update$35(CoursierDependencyResolution.scala:218)
  [build] [error] 	at scala.util.Either$LeftProjection.map(Either.scala:573)
  [build] [error] 	at lmcoursier.CoursierDependencyResolution.update(CoursierDependencyResolution.scala:218)
  [build] [error] 	at sbt.librarymanagement.DependencyResolution.update(DependencyResolution.scala:60)
  [build] [error] 	at sbt.internal.LibraryManagement$.resolve$1(LibraryManagement.scala:52)
  [build] [error] 	at sbt.internal.LibraryManagement$.$anonfun$cachedUpdate$12(LibraryManagement.scala:102)
  [build] [error] 	at sbt.util.Tracked$.$anonfun$lastOutput$1(Tracked.scala:69)
  [build] [error] 	at sbt.internal.LibraryManagement$.$anonfun$cachedUpdate$20(LibraryManagement.scala:115)
  [build] [error] 	at scala.util.control.Exception$Catch.apply(Exception.scala:228)
  [build] [error] 	at sbt.internal.LibraryManagement$.$anonfun$cachedUpdate$11(LibraryManagement.scala:115)
  [build] [error] 	at sbt.internal.LibraryManagement$.$anonfun$cachedUpdate$11$adapted(LibraryManagement.scala:96)
  [build] [error] 	at sbt.util.Tracked$.$anonfun$inputChanged$1(Tracked.scala:150)
  [build] [error] 	at sbt.internal.LibraryManagement$.cachedUpdate(LibraryManagement.scala:129)
  [build] [error] 	at sbt.Classpaths$.$anonfun$updateTask0$5(Defaults.scala:2950)
  [build] [error] 	at scala.Function1.$anonfun$compose$1(Function1.scala:49)
  [build] [error] 	at sbt.internal.util.$tilde$greater.$anonfun$$u2219$1(TypeFunctions.scala:62)
  [build] [error] 	at sbt.std.Transform$$anon$4.work(Transform.scala:67)
  [build] [error] 	at sbt.Execute.$anonfun$submit$2(Execute.scala:281)
  [build] [error] 	at sbt.internal.util.ErrorHandling$.wideConvert(ErrorHandling.scala:19)
  [build] [error] 	at sbt.Execute.work(Execute.scala:290)
  [build] [error] 	at sbt.Execute.$anonfun$submit$1(Execute.scala:281)
  [build] [error] 	at sbt.ConcurrentRestrictions$$anon$4.$anonfun$submitValid$1(ConcurrentRestrictions.scala:178)
  [build] [error] 	at sbt.CompletionService$$anon$2.call(CompletionService.scala:37)
  [build] [error] 	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
  [build] [error] 	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
  [build] [error] 	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
  [build] [error] 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
  [build] [error] 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
  [build] [error] 	at java.base/java.lang.Thread.run(Thread.java:834)
  [build] [error] (update) sbt.librarymanagement.ResolveException: Error downloading com.typesafe.sbt:sbt-native-packager;sbtVersion=1.0;scalaVersion=2.12:1.7.5
  [build] [error]   Not found
  [build] [error]   Not found
  [build] [error]   not found: https://repo1.maven.org/maven2/com/typesafe/sbt/sbt-native-packager_2.12_1.0/1.7.5/sbt-native-packager-1.7.5.pom
  [build] [error]   not found: /home/cnb/.ivy2/local/com.typesafe.sbt/sbt-native-packager/scala_2.12/sbt_1.0/1.7.5/ivys/ivy.xml
  [build] [error]   download error: Caught java.net.UnknownHostException: repo.scala-sbt.org (repo.scala-sbt.org) while downloading https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/com.typesafe.sbt/sbt-native-packager/scala_2.12/sbt_1.0/1.7.5/ivys/ivy.xml
  [build] [error]   not found: https://repo.typesafe.com/typesafe/ivy-releases/com.typesafe.sbt/sbt-native-packager/scala_2.12/sbt_1.0/1.7.5/ivys/ivy.xml
  [build] [error] Error downloading io.spray:sbt-revolver;sbtVersion=1.0;scalaVersion=2.12:0.9.1
  [build] [error]   Not found
  [build] [error]   Not found
  [build] [error]   not found: https://repo1.maven.org/maven2/io/spray/sbt-revolver_2.12_1.0/0.9.1/sbt-revolver-0.9.1.pom
  [build] [error]   not found: /home/cnb/.ivy2/local/io.spray/sbt-revolver/scala_2.12/sbt_1.0/0.9.1/ivys/ivy.xml
  [build] [error]   download error: Caught java.net.UnknownHostException: repo.scala-sbt.org (repo.scala-sbt.org) while downloading https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/io.spray/sbt-revolver/scala_2.12/sbt_1.0/0.9.1/ivys/ivy.xml
  [build] [error]   not found: https://repo.typesafe.com/typesafe/ivy-releases/io.spray/sbt-revolver/scala_2.12/sbt_1.0/0.9.1/ivys/ivy.xml
  [build] Project loading failed: (r)etry, (q)uit, (l)ast, or (i)gnore? rpc error: code = NotFound desc = an error occurred when try to find container "2285ed81062d424744b4219b849c1146ff5a1347be595f164d052f7b8e1f09a9": not found

You can see full logs here: https://github.com/mattmoor/mink/runs/1370168466?check_suite_focus=true#step:11:37897

Failure: 'Test All Samples' workflow

Test nginx workflow failed. Please take a look to ensure samples are working. (cc @paketo-buildpacks/content-maintainers)

Add sample Go app where it is an app that imports no module

Currently there is no sample that shows the no modules workflow of the Go Buildpack. We should add an app that shows this workflow.

go/mod example failing with errors

What happened?

• What were you attempting to do?

Build using tekton

• What did you expect to happen?

Produce a valid container image

• What was the actual behavior? Please provide log output, if possible.

An error message occured...

err:  paketo-buildpacks/[email protected]
======== Error: paketo-buildpacks/[email protected] ========
chdir /workspace/source/java/go-mod: no such file or directory
======== Error: paketo-buildpacks/[email protected] ========
chdir /workspace/source/java/go-mod: no such file or directory
======== Error: paketo-buildpacks/[email protected] ========
chdir /workspace/source/java/go-mod: no such file or directory
======== Error: paketo-buildpacks/[email protected] ========
chdir /workspace/source/java/go-mod: no such file or directory
======== Error: paketo-buildpacks/[email protected] ========
chdir /workspace/source/java/go-mod: no such file or directory
======== Error: paketo-buildpacks/[email protected] ========
chdir /workspace/source/java/go-mod: no such file or directory
======== Error: paketo-buildpacks/[email protected] ========
chdir /workspace/source/java/go-mod: no such file or directory
======== Error: paketo-buildpacks/[email protected] ========
chdir /workspace/source/java/go-mod: no such file or directory
======== Error: paketo-buildpacks/[email protected] ========
chdir /workspace/source/java/go-mod: no such file or directory
======== Error: paketo-buildpacks/[email protected] ========
chdir /workspace/source/java/go-mod: no such file or directory
======== Error: paketo-buildpacks/[email protected] ========
chdir /workspace/source/java/go-mod: no such file or directory
======== Error: paketo-buildpacks/[email protected] ========
chdir /workspace/source/java/go-mod: no such file or directory
======== Error: paketo-buildpacks/[email protected] ========
chdir /workspace/source/java/go-mod: no such file or directory
======== Error: paketo-buildpacks/[email protected] ========
chdir /workspace/source/java/go-mod: no such file or directory
======== Error: paketo-buildpacks/[email protected] ========
chdir /workspace/source/java/go-mod: no such file or directory
======== Error: paketo-buildpacks/[email protected] ========
chdir /workspace/source/java/go-mod: no such file or directory
======== Error: paketo-buildpacks/[email protected] ========
chdir /workspace/source/java/go-mod: no such file or directory
======== Error: paketo-buildpacks/[email protected] ========
chdir /workspace/source/java/go-mod: no such file or directory

Build Configuration

• What platform (pack, kpack, tekton buildpacks plugin, etc.) are you
  using? Please include a version.

tekton 0.3

• What buildpacks are you using? Please include versions.

go buildpack

• What builder are you using? If custom, can you provide the output from pack inspect-builder <builder>?

base-builder

• Can you provide a sample app or relevant configuration (buildpack.yml,
  nginx.conf, etc.)?

https://github.com/paketo-buildpacks/samples/tree/main/go/mod

Checklist

• I have included log output.
• The log output includes an error message.

Test HTTPD samples with the base builder

We recently added support for httpd to the base stack and we're getting ready to update the base builder. Once that's done, we should update the web-servers test to run with the base builder.

Node.js samples should not reference "main" in package.json

The "main" field in the package.json file is used to indicate an entrypoint for a node module. This only applies to library code and is not meant to indicate the entrypoint of an application. Furthermore, the Node.js language family does not have any mechanism to choose a start command using the "main" field if it did indicate the application's entrypoint.

The current Node.js sample applications include this key:

samples/nodejs/npm/package.json

Line 8 in 7d3ea57

"main": "server.js",

samples/nodejs/yarn/package.json

Line 8 in 7d3ea57

"main": "server.js",

It is confusing to users that this "main" field appears in the package.json, as it may lead some users to believe they can control the start command by changing this value.

These values should be removed from all Node.js sample applications so that this possible confusion is avoided.

Slack Conversation

Failure: 'Test All Samples' workflow

Test web-servers workflow failed. Please take a look to ensure samples are working. (cc @paketo-buildpacks/content-maintainers)

Add Sample apps for all configurations supported by .NET Core buildpack

What happened?

The re-architected .NET Core buildpack supports builds of the following configurations:

• source-based
• self-contained
• framework-dependent deployment/executable

We currently just have sample apps for source-based ASP.NET and runtime apps; Could we look into adding some simple apps for all supported configurations?

Failure: 'Test All Samples' workflow

Test nginx workflow failed. Please take a look to ensure samples are working. (cc @paketo-buildpacks/content-maintainers)

(Automatically) update pack version used for tests

What happened?

Currently, the pack version used by tests is determined by .github/pack-version, and the version is very out of date. As a result, tests for the Go samples fail because apps are built without a default process type.

This repo should follow other repos' conventions of keeping a tools.json in its scripts directory and should have a cron job that keeps that tools.json automatically up to date.

Checklist

• I have included log output.
• The log output includes an error message.
• I have included steps for reproduction.

Assert that sample apps work with the latest builders

What happened?

• What were you attempting to do?
  I was trying to confirm that the set of samples provided in this repo can be built with the current builders.

• What did you expect to happen?
  I expected that there would be a set of tests that I could run to confirm this.

• What was the actual behavior? Please provide log output, if possible.
  There are no tests, and so I need to try to confirm this in an ad-hoc manner.

Checklist

• I have included log output.
• The log output includes an error message.
• I have included steps for reproduction.

Take stock / update PHP samples

With the PHP rewrite coming to a close, we should take stock of the sample apps we have for the PHP language family, and update/add anything to give clear examples of apps that can be run with the three order groups available from the rewrite.

This issue is blocked from completion on the completion and release of paketo-buildpacks/php#524

Document that PHP sample apps need the full builder

What happened?

We should document that users should use the Full builder to build all of our PHP sample apps. Building with Base succeeds, but I see obscure errors for missing C libraries when I try to run the app.

Add samples app to demonstrate NGINX Zero Config features

Once paketo-buildpacks/nginx#367 merges and is released, we should include a sample/samples here that demonstrate how to use the nginx.conf generation feature of the NGINX buildpack.

Add samples app to demonstrate HTTPD Zero Config features

BLOCKED ON MERGE paketo-buildpacks/httpd#306

Once the above PR is merged then the functionality outlined in Paketo Web Server RFC 0004 will be complete and there should be sample(s) to demonstrate this functionality.

Failure: 'Test All Samples' workflow

Test web-servers workflow failed. Please take a look to ensure samples are working. (cc @paketo-buildpacks/content-maintainers)

Failure: 'Test All Samples' workflow

Test web-servers workflow failed. Please take a look to ensure samples are working. (cc @paketo-buildpacks/content-maintainers)

Failure: 'Test All Samples' workflow

Test web-servers workflow failed. Please take a look to ensure samples are working. (cc @paketo-buildpacks/content-maintainers)

No sample app that demos the use of php composer

It would be useful to see a sample app that demos php-composer

akka sample doesn't listen on 8080

This shows --publish 8080:8080, but from what I can tell the code doesn't listen on HTTP at all, and this is after deploying to Knative where it times out after 2 minutes of TCP connect errors on 8080 😅

I also reached out to some folks that know akka better than my "no at all", and they seemed to think the same (doesn't bind to http server).

I think this sample should either remove the --publish or (better IMO) demonstrate the same HTTP capabilities in akka.

Add Ruby Sample Apps

Now that the Ruby Promotion RFC has been accepted, we should add in sample apps here for all supported configurations of the Ruby Buildpack.

Failure: 'Test All Samples' workflow

Test nginx workflow failed. Please take a look to ensure samples are working. (cc @paketo-buildpacks/content-maintainers)

Failure: 'Test All Samples' workflow

Test web-servers workflow failed. Please take a look to ensure samples are working. (cc @paketo-buildpacks/content-maintainers)

Add Java sample apps

It would be great if we could have some sample Java apps for various configurations so that we have sample apps for all supported Paketo language families.

Failure: 'Test All Samples' workflow

Test php workflow failed. Please take a look to ensure samples are working. (cc @paketo-buildpacks/content-maintainers)

Add Web Servers Samples

Now that Web Servers RFC 0005 has been accepted, this repo should contain samples using the Web Servers buildpack.

• A new web-servers top level directory should be created.
• The httpd samples should be moved into this directory.
• A copy of nginx samples should be added to the directory. (Since httpd does not run on the base builder, a copy of thenginx samples should also be kept in their own top level directory, so they can continue to be tested against the base builder.)
• The react sample should be moved to the web servers directory.
• Be sure to follow the instructions in the Adding New Samples section of the readme

Add sample Node.js app that has no node modules

Currently there is no sample that shows the node only workflow of the Node.js Buildpack. We should add an app that shows this workflow.

Builder Compatibility Documentation

We should figure out a way to indicate the builders that are compatible to run each sample app. This would help reduce confusion for new buildpacks users and make it more clear the clear that each language family is compatible with and in what circumstance it is compatible with a given builder .