Skip to content

Adapted link to changed buildpack structure #531

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.

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

Merged
merged 2 commits into from
Oct 24, 2024
Merged
Changes from all commits
Commits
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
18 changes: 18 additions & 0 deletions deploy-apps/manifest-attributes.html.md.erb
Original file line number Diff line number Diff line change
Expand Up @@ -368,6 +368,24 @@ The default number of instances is 1.

To ensure that platform maintenance does not interrupt your app, <%= vars.recommended_by %> recommends running at least two instances.

### <a id='lifecycle'></a> lifecycle

The `lifecycle` attribute specifies which application lifecycle to use for staging and running the application. Three variants are supported at the moment:

- [`buildpack`](../../buildpacks/classic.html)
- [`cnb`](../../buildpacks/cnb/index.html)
- [`docker`](push-docker.html)

For example:

```
---
...
lifecycle: buildpack
```

The default is `buildpack` unless the [`docker`](#docker) attribute is specified.

### <a id='log-rate-limit-per-second'></a> log-rate-limit-per-second

The `log-rate-limit-per-second` attribute specifies the log rate limit for all instances of an app. This attribute requires a unit of measurement: `B`, `K`, `KB`, `M`, `MB`, `G`, or `GB`, in either uppercase or lowercase.
Expand Down