Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update specify-launch-process docs #762

Merged
merged 1 commit into from
Aug 28, 2024
Merged

Update specify-launch-process docs #762

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/docs/for-app-developers/how-to/build-outputs/specify-launch-process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ Rebasable: true

Buildpacks:
ID VERSION HOMEPAGE
samples/java-maven 0.0.1 https://github.com/buildpacks/samples/tree/main/buildpacks/java-maven
samples/java-maven 0.0.2 https://github.com/buildpacks/samples/tree/main/buildpacks/java-maven
samples/hello-processes 0.0.1 https://github.com/buildpacks/samples/tree/main/buildpacks/hello-process

Processes:
Expand All @@ -63,7 +63,7 @@ Processes:
sys-info bash /layers/samples_hello-processes/sys-info/sys-info.sh
```

Notice that the default process type is `web`. This is because `pack` will always attempt to set the default process type to `web` unless the `--default-process` flag is passed.
Notice that the `java-maven` buildpack defined `web` as the default process type.
If we had run the `pack build` command above with `--default-process sys-info`, `sys-info` would be the default process for the app image!

### Run a multi-process app
Expand Down
Loading