Skip to content

Commit

Permalink
Update tutorials (#77)
Browse files Browse the repository at this point in the history 
Co-authored-by: heroku-linguist[bot] <136119646+heroku-linguist[bot]@users.noreply.github.com>
  • Loading branch information
@heroku-linguist
heroku-linguist[bot] authored Dec 25, 2024
1 parent fd7493d commit 27b16e7
Show file tree
Hide file tree
Showing 9 changed files with 288 additions and 258 deletions.
44 changes: 25 additions & 19 deletions docs/dotnet/README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -129,7 +129,7 @@ Image with name "my-image-name" not found
===> DETECTING
2 of 3 buildpacks participating
heroku/dotnet 0.1.9
heroku/procfile 3.1.2
heroku/procfile 3.2.0
===> RESTORING
Skipping buildpack layer analysis
===> BUILDING
Expand All @@ -142,15 +142,15 @@ Skipping buildpack layer analysis
- Detected version requirement: `^8.0`
- Resolved .NET SDK version `8.0.404` (linux-amd64)
- SDK installation
- Downloading SDK from https://download.visualstudio.microsoft.com/download/pr/4e3b04aa-c015-4e06-a42e-05f9f3c54ed2/74d1bb68e330eea13ecfc47f7cf9aeb7/dotnet-sdk-8.0.404-linux-x64.tar.gz ... (0.5s)
- Downloading SDK from https://download.visualstudio.microsoft.com/download/pr/4e3b04aa-c015-4e06-a42e-05f9f3c54ed2/74d1bb68e330eea13ecfc47f7cf9aeb7/dotnet-sdk-8.0.404-linux-x64.tar.gz ... (0.7s)
- Verifying SDK checksum
- Installing SDK
- Publish solution
- Using `Release` build configuration
- Running `dotnet publish /workspace/GettingStarted.sln --runtime linux-x64 "-p:PublishDir=bin/publish"`
Determining projects to restore...
Restored /workspace/Frontend/Frontend.csproj (in 10.85 sec).
Restored /workspace/Frontend/Frontend.csproj (in 11.42 sec).
Frontend -> /workspace/Frontend/bin/Release/net8.0/linux-x64/Frontend.dll
Frontend -> /workspace/Frontend/bin/publish/
Restoring .NET tools
Expand All @@ -164,14 +164,17 @@ Skipping buildpack layer analysis
Done. Migrations Bundle: /workspace/Frontend/bin/publish/efbundle
Don't forget to copy appsettings.json alongside your bundle if you need it to apply migrations.
- Done (27.7s)
- Done (28.5s)
- Setting launch table
- Detecting process types from published artifacts
- Added `Frontend`: bash -c cd Frontend/bin/publish; ./Frontend --urls http://*:$PORT
- Done (finished in 31.7s)
- Done (finished in 32.6s)
[Discovering process types]
Procfile declares types -> web
## Procfile Buildpack
- Processes from `Procfile`
- web: `cd Frontend/bin/publish/; ./Frontend --urls http://*:$PORT`
- Done (finished in < 0.1s)
===> EXPORTING
Adding layer 'heroku/dotnet:runtime'
Adding layer 'buildpacksio/lifecycle:launch.sbom'
Expand All @@ -184,7 +187,7 @@ Adding label 'io.buildpacks.build.metadata'
Adding label 'io.buildpacks.project.metadata'
Setting default process type 'web'
Saving my-image-name...
*** Images (460038f7aef8):
*** Images (934d2192b298):
my-image-name
Adding cache layer 'heroku/dotnet:nuget-cache'
Adding cache layer 'heroku/dotnet:sdk'
Expand All @@ -199,7 +202,7 @@ Verify that you see “Successfully built image my-image-name” at the end of t

```
$ docker image ls --format "table {{.ID}}\t{{.Repository}}\t{{.Tag}}" | grep my-image-name
460038f7aef8 my-image-name latest
934d2192b298 my-image-name latest
```
<!-- STOP. This document is autogenerated. Do not manually modify. See the top of the doc for more details. -->
## What does `pack build` do?
Expand All @@ -214,7 +217,7 @@ When you run `pack build` with a builder, each buildpack runs a detection script
===> DETECTING
2 of 3 buildpacks participating
heroku/dotnet 0.1.9
heroku/procfile 3.1.2
heroku/procfile 3.2.0
===> RESTORING
Skipping buildpack layer analysis
```
Expand All @@ -239,7 +242,7 @@ $ docker run -it --rm --env PORT=5006 -p 5006:5006 my-image-name
warn: Microsoft.AspNetCore.DataProtection.Repositories.FileSystemXmlRepository[60]
Storing keys in a directory '/home/heroku/.aspnet/DataProtection-Keys' that may not be persisted outside of the container. Protected data will be unavailable when container is destroyed. For more information go to https://aka.ms/aspnet/dataprotectionwarning
warn: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[35]
No XML encryptor configured. Key {870dba38-88f8-4e25-a58c-ef9523d2d0fb} may be persisted to storage in unencrypted form.
No XML encryptor configured. Key {95818f5f-5e43-4786-bcd2-086ffcfd1654} may be persisted to storage in unencrypted form.
info: Microsoft.Hosting.Lifetime[14]
Now listening on: http://[::]:5006
info: Microsoft.Hosting.Lifetime[0]
Expand Down Expand Up @@ -393,7 +396,7 @@ Image with name "my-image-name" not found
===> DETECTING
heroku/python 0.21.0
heroku/dotnet 0.1.9
heroku/procfile 3.1.2
heroku/procfile 3.2.0
===> RESTORING
Skipping buildpack layer analysis
===> BUILDING
Expand Down Expand Up @@ -421,15 +424,15 @@ Running 'pip install -r requirements.txt'
- Detected version requirement: `^8.0`
- Resolved .NET SDK version `8.0.404` (linux-amd64)
- SDK installation
- Downloading SDK from https://download.visualstudio.microsoft.com/download/pr/4e3b04aa-c015-4e06-a42e-05f9f3c54ed2/74d1bb68e330eea13ecfc47f7cf9aeb7/dotnet-sdk-8.0.404-linux-x64.tar.gz ... (0.6s)
- Downloading SDK from https://download.visualstudio.microsoft.com/download/pr/4e3b04aa-c015-4e06-a42e-05f9f3c54ed2/74d1bb68e330eea13ecfc47f7cf9aeb7/dotnet-sdk-8.0.404-linux-x64.tar.gz ... (0.9s)
- Verifying SDK checksum
- Installing SDK
- Publish solution
- Using `Release` build configuration
- Running `dotnet publish /workspace/GettingStarted.sln --runtime linux-x64 "-p:PublishDir=bin/publish"`
Determining projects to restore...
Restored /workspace/Frontend/Frontend.csproj (in 15.61 sec).
Restored /workspace/Frontend/Frontend.csproj (in 11.57 sec).
Frontend -> /workspace/Frontend/bin/Release/net8.0/linux-x64/Frontend.dll
Frontend -> /workspace/Frontend/bin/publish/
Restoring .NET tools
Expand All @@ -443,14 +446,17 @@ Running 'pip install -r requirements.txt'
Done. Migrations Bundle: /workspace/Frontend/bin/publish/efbundle
Don't forget to copy appsettings.json alongside your bundle if you need it to apply migrations.
- Done (32.3s)
- Done (28.3s)
- Setting launch table
- Detecting process types from published artifacts
- Added `Frontend`: bash -c cd Frontend/bin/publish; ./Frontend --urls http://*:$PORT
- Done (finished in 36.3s)
- Done (finished in 32.6s)
## Procfile Buildpack
[Discovering process types]
Procfile declares types -> web
- Processes from `Procfile`
- web: `cd Frontend/bin/publish/; ./Frontend --urls http://*:$PORT`
- Done (finished in < 0.1s)
===> EXPORTING
Adding layer 'heroku/python:python'
Adding layer 'heroku/python:venv'
Expand All @@ -465,7 +471,7 @@ Adding label 'io.buildpacks.build.metadata'
Adding label 'io.buildpacks.project.metadata'
Setting default process type 'web'
Saving my-image-name...
*** Images (213140c1c125):
*** Images (937703a6ee96):
my-image-name
Adding cache layer 'heroku/python:pip'
Adding cache layer 'heroku/python:pip-cache'
Expand Down
19 changes: 11 additions & 8 deletions docs/go/README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -135,7 +135,7 @@ Image with name "my-image-name" not found
===> DETECTING
2 of 3 buildpacks participating
heroku/go 0.5.0
heroku/procfile 3.1.2
heroku/procfile 3.2.0
===> RESTORING
Skipping buildpack layer analysis
===> BUILDING
Expand All @@ -155,8 +155,11 @@ Building packages:
- github.com/heroku/go-getting-started
Skipping launch process registration (Procfile detected)
[Discovering process types]
Procfile declares types -> web
## Procfile Buildpack
- Processes from `Procfile`
- web: `go-getting-started`
- Done (finished in < 0.1s)
===> EXPORTING
Adding layer 'heroku/go:go_target'
Adding layer 'buildpacksio/lifecycle:launch.sbom'
Expand All @@ -169,7 +172,7 @@ Adding label 'io.buildpacks.build.metadata'
Adding label 'io.buildpacks.project.metadata'
Setting default process type 'web'
Saving my-image-name...
*** Images (8310503d57b9):
*** Images (4280729e8ce2):
my-image-name
Adding cache layer 'heroku/go:go_build'
Adding cache layer 'heroku/go:go_dist'
Expand All @@ -184,7 +187,7 @@ Verify that you see “Successfully built image my-image-name” at the end of t

```
$ docker image ls --format "table {{.ID}}\t{{.Repository}}\t{{.Tag}}" | grep my-image-name
8310503d57b9 my-image-name latest
4280729e8ce2 my-image-name latest
```
<!-- STOP. This document is autogenerated. Do not manually modify. See the top of the doc for more details. -->
## What does `pack build` do?
Expand All @@ -199,7 +202,7 @@ When you run `pack build` with a builder, each buildpack runs a detection script
===> DETECTING
2 of 3 buildpacks participating
heroku/go 0.5.0
heroku/procfile 3.1.2
heroku/procfile 3.2.0
===> RESTORING
Skipping buildpack layer analysis
```
Expand All @@ -226,10 +229,10 @@ $ docker run -it --rm --env PORT=5006 -p 5006:5006 my-image-name
- using code: gin.SetMode(gin.ReleaseMode)
[GIN-debug] Loaded HTML Templates (4):
-
- header.tmpl.html
- index.tmpl.html
- nav.tmpl.html
-
- header.tmpl.html
[GIN-debug] GET /static/*filepath --> github.com/gin-gonic/gin.(*RouterGroup).createStaticHandler.func1 (2 handlers)
[GIN-debug] HEAD /static/*filepath --> github.com/gin-gonic/gin.(*RouterGroup).createStaticHandler.func1 (2 handlers)
Expand Down
35 changes: 19 additions & 16 deletions docs/java_gradle/README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -134,7 +134,7 @@ Image with name "my-image-name" not found
3 of 4 buildpacks participating
heroku/jvm 6.0.4
heroku/gradle 6.0.4
heroku/procfile 3.1.2
heroku/procfile 3.2.0
===> RESTORING
Skipping buildpack layer analysis
===> BUILDING
Expand Down Expand Up @@ -167,8 +167,11 @@ BUILD SUCCESSFUL in 6s
5 actionable tasks: 5 executed
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
[Discovering process types]
Procfile declares types -> web
## Procfile Buildpack
- Processes from `Procfile`
- web: `java -jar build/libs/java-getting-started-gradle-1.0.0-SNAPSHOT.jar`
- Done (finished in < 0.1s)
===> EXPORTING
Adding layer 'heroku/jvm:openjdk'
Adding layer 'heroku/jvm:runtime'
Expand All @@ -183,7 +186,7 @@ Adding label 'io.buildpacks.build.metadata'
Adding label 'io.buildpacks.project.metadata'
Setting default process type 'web'
Saving my-image-name...
*** Images (ba902c19a946):
*** Images (837787fc6af2):
my-image-name
Adding cache layer 'heroku/jvm:openjdk'
Adding cache layer 'heroku/gradle:home'
Expand All @@ -198,7 +201,7 @@ Verify that you see “Successfully built image my-image-name” at the end of t

```
$ docker image ls --format "table {{.ID}}\t{{.Repository}}\t{{.Tag}}" | grep my-image-name
ba902c19a946 my-image-name latest
837787fc6af2 my-image-name latest
```
<!-- STOP. This document is autogenerated. Do not manually modify. See the top of the doc for more details. -->
## What does `pack build` do?
Expand All @@ -214,7 +217,7 @@ When you run `pack build` with a builder, each buildpack runs a detection script
3 of 4 buildpacks participating
heroku/jvm 6.0.4
heroku/gradle 6.0.4
heroku/procfile 3.1.2
heroku/procfile 3.2.0
===> RESTORING
```
<!-- STOP. This document is autogenerated. Do not manually modify. See the top of the doc for more details. -->
Expand Down Expand Up @@ -245,16 +248,16 @@ Picked up JAVA_TOOL_OPTIONS: -XX:MaxRAMPercentage=80.0 -Dfile.encoding=UTF-8
:: Built with Spring Boot :: 3.3.5
2024-12-18T16:38:02.994Z INFO 1 --- [ main] c.heroku.java.GettingStartedApplication : Starting GettingStartedApplication v1.0.0-SNAPSHOT using Java 17.0.13 with PID 1 (/workspace/build/libs/java-getting-started-gradle-1.0.0-SNAPSHOT.jar started by heroku in /workspace)
2024-12-18T16:38:03.001Z INFO 1 --- [ main] c.heroku.java.GettingStartedApplication : No active profile set, falling back to 1 default profile: "default"
2024-12-18T16:38:04.075Z INFO 1 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port 5006 (http)
2024-12-18T16:38:04.090Z INFO 1 --- [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat]
2024-12-18T16:38:04.090Z INFO 1 --- [ main] o.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/10.1.31]
2024-12-18T16:38:04.128Z INFO 1 --- [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext
2024-12-18T16:38:04.130Z INFO 1 --- [ main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 1052 ms
2024-12-18T16:38:04.260Z INFO 1 --- [ main] o.s.b.a.w.s.WelcomePageHandlerMapping : Adding welcome page template: index
2024-12-18T16:38:04.595Z INFO 1 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port 5006 (http) with context path '/'
2024-12-18T16:38:04.612Z INFO 1 --- [ main] c.heroku.java.GettingStartedApplication : Started GettingStartedApplication in 2.006 seconds (process running for 2.471)
2024-12-23T00:33:56.722Z INFO 1 --- [ main] c.heroku.java.GettingStartedApplication : Starting GettingStartedApplication v1.0.0-SNAPSHOT using Java 17.0.13 with PID 1 (/workspace/build/libs/java-getting-started-gradle-1.0.0-SNAPSHOT.jar started by heroku in /workspace)
2024-12-23T00:33:56.726Z INFO 1 --- [ main] c.heroku.java.GettingStartedApplication : No active profile set, falling back to 1 default profile: "default"
2024-12-23T00:33:57.773Z INFO 1 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port 5006 (http)
2024-12-23T00:33:57.787Z INFO 1 --- [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat]
2024-12-23T00:33:57.788Z INFO 1 --- [ main] o.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/10.1.31]
2024-12-23T00:33:57.827Z INFO 1 --- [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext
2024-12-23T00:33:57.828Z INFO 1 --- [ main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 1041 ms
2024-12-23T00:33:57.958Z INFO 1 --- [ main] o.s.b.a.w.s.WelcomePageHandlerMapping : Adding welcome page template: index
2024-12-23T00:33:58.308Z INFO 1 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port 5006 (http) with context path '/'
2024-12-23T00:33:58.325Z INFO 1 --- [ main] c.heroku.java.GettingStartedApplication : Started GettingStartedApplication in 2.008 seconds (process running for 2.467)
```
<!-- STOP. This document is autogenerated. Do not manually modify. See the top of the doc for more details. -->

Expand Down
Loading

0 comments on commit 27b16e7

Please sign in to comment.