Skip to content

Update configuration.html.markerb #1996

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

Merged
merged 2 commits into from
Jun 25, 2025
+1 −1
Merged

Update configuration.html.markerb #1996

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a4063da
Update configuration.html.markerb
leburgeon Apr 9, 2025
5eef0a1
add small edit
kcmartin Jun 25, 2025
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
2 changes: 1 addition & 1 deletion reference/configuration.html.markerb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@
primary_region = "ord"
```

## Runtime options

Check failure on line 49 in reference/configuration.html.markerb

View workflow job for this annotation

GitHub Actions / Vale linter 

[vale] reported by reviewdog 🐶
[Vale.Terms] Use 'runtimes?\b' instead of 'Runtime'.

Raw Output:
{"message": "[Vale.Terms] Use 'runtimes?\\b' instead of 'Runtime'.", "location": {"path": "reference/configuration.html.markerb", "range": {"start": {"line": 49, "column": 4}}}, "severity": "ERROR"}

The following options are available to control the lifecycle of a running application. These are optional and can be placed at the top level of the `fly.toml` file:

Expand Down Expand Up @@ -100,7 +100,7 @@
buildpacks = ["gcr.io/paketo-buildpacks/nodejs"]
```

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.

Check failure on line 103 in reference/configuration.html.markerb

View workflow job for this annotation

GitHub Actions / Vale linter 

[vale] reported by reviewdog 🐶
[Vale.Terms] Use 'buildpacks?\b' instead of 'Buildpacks'.

Raw Output:
{"message": "[Vale.Terms] Use 'buildpacks?\\b' instead of 'Buildpacks'.", "location": {"path": "reference/configuration.html.markerb", "range": {"start": {"line": 103, "column": 32}}}, "severity": "ERROR"}

In our example above, the builder is being set to use [Paketo's all-purpose builder](https://paketo.io) with the NodeJS buildpack.

Expand Down Expand Up @@ -148,7 +148,7 @@

### Specify Docker build arguments

You can pass [build-time arguments](https://docs.docker.com/engine/reference/commandline/build/#set-build-time-variables---build-arg) to both Dockerfile and Buildpack builds using the `[build.args]` sub-section:

Check failure on line 151 in reference/configuration.html.markerb

View workflow job for this annotation

GitHub Actions / Vale linter 

[vale] reported by reviewdog 🐶
[Vale.Terms] Use 'buildpacks?\b' instead of 'Buildpack'.

Raw Output:
{"message": "[Vale.Terms] Use 'buildpacks?\\b' instead of 'Buildpack'.", "location": {"path": "reference/configuration.html.markerb", "range": {"start": {"line": 151, "column": 158}}}, "severity": "ERROR"}

```toml
[build.args]
Expand Down Expand Up @@ -402,7 +402,7 @@
Times are in milliseconds unless units are specified.

* `grace_period`: The time to wait after a Machine starts before checking its health. Make sure this is long enough for your app to start up. For example, if your app takes 2 seconds to start up, give it some runway by setting `grace_period` to at least 3 seconds.
* `interval`: The time between connectivity checks. There should be a balance between the interval and the grace period. If it's long and your grace_period shorter than your app's startup time, health check will take too long adding you your deployment time.
* `interval`: The time between connectivity checks. There should be a balance between the interval and the grace period. If interval is long and grace_period is shorter than your app's startup time, the health check will take too long, adding to your deployment time.
* `timeout`: The maximum time a connection can take before being reported as failing its health check.
* `method`: The HTTP method to be used for the check. If omitted, the default is `get`.
* `path`: The path of the URL to be requested.
Expand Down
Loading