You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -27,15 +27,39 @@ The following are _very_ simple examples for deploying the artifact types that w
27
27
## Configuration and Extension
28
28
The buildpack supports extension through the use of Git repository forking. The easiest way to accomplish this is to use [GitHub's forking functionality][] to create a copy of this repository. Make the required extension changes in the copy of the repository. Then specify the URL of the new repository when pushing Cloud Foundry applications. If the modifications are generally applicable to the Cloud Foundry community, please submit a [pull request][] with the changes.
29
29
30
-
Buildpack configuration can be overridden with an environment variable matching the configuration file you wish to override minus the `.yml` extension and with a prefix of `JBP_CONFIG`. It is not possible to add new configuration properties and properties with `nil` or empty values will be ignored by the buildpack. The value of the variable should be valid inline yaml. For example, to change the default version of Java to 7 and adjust the memory heuristics apply this environment variable to the application.
30
+
Buildpack configuration can be overridden with an environment variable matching the configuration file you wish to override minus the `.yml` extension and with a prefix of `JBP_CONFIG`. It is not possible to add new configuration properties and properties with `nil` or empty values will be ignored by the buildpack. The value of the variable should be valid inline yaml, referred to as `flow style` in the yaml spec ([Wikipedia] has a good description of this yaml syntax). For example, to change the default version of Java to 7 and adjust the memory heuristics apply this environment variable to the application.
If the key or value contains a special character such as `:` it should be escaped with double quotes. For example, to change the default repository path for the buildpack.
If the key or value contains an environment variable that you want to bind at runtime you need to escape it from your shell. For example, to add command line arguments containing an environment variable to a [Java Main](docs/container-java_main.md) application.
Environment variable can also be specified in the applications `manifest` file. For example, to specify an environment variable in an applications manifest file that disables Auto-reconfiguration.
37
49
38
-
Environment variable can also be specified in the applications `manifest` file. See the [Environment Variables][] documentation for more information.
This final example shows how to change the version of Tomcat that is used by the buildpack with an environment variable specified in the applications manifest file.
56
+
57
+
```bash
58
+
env:
59
+
JBP_CONFIG_TOMCAT: '{tomcat: { version: 8.0.+ }}'
60
+
```
61
+
62
+
See the [Environment Variables][] documentation for more information.
39
63
40
64
To learn how to configure various properties of the buildpack, follow the "Configuration" links below. More information on extending the buildpack is available [here](docs/extending.md).
41
65
@@ -53,17 +77,21 @@ To learn how to configure various properties of the buildpack, follow the "Confi
* [Spring Auto Reconfiguration](docs/framework-spring_auto_reconfiguration.md) ([Configuration](docs/framework-spring_auto_reconfiguration.md#configuration))
@@ -91,8 +119,8 @@ The buildpack can be packaged up so that it can be uploaded to Cloud Foundry usi
91
119
The online package is a version of the buildpack that is as minimal as possible and is configured to connect to the network for all dependencies. This package is about 50K in size. To create the online package, run:
92
120
93
121
```bash
94
-
bundle install
95
-
bundle exec rake package
122
+
$ bundle install
123
+
$ bundle exec rake package
96
124
...
97
125
Creating build/java-buildpack-cfd6b17.zip
98
126
```
@@ -103,8 +131,8 @@ The offline package is a version of the buildpack designed to run without access
103
131
To pin the version of dependencies used by the buildpack to the ones currently resolvable use the `PINNED=true` argument. This will update the [`config/` directory][] to contain exact version of each dependency instead of version ranges.
Keeping track of different versions of the buildpack can be difficult. To help with this, the rake `package` task puts a version discriminator in the name of the created package file. The default value for this discriminator is the current Git hash (e.g. `cfd6b17`). To change the version when creating a package, use the `VERSION=<VERSION>` argument:
0 commit comments