From 8a9c13dbfa26a94aa829db71e0b9bc6e39eb8f6b Mon Sep 17 00:00:00 2001 From: Arthur De Magalhaes Date: Mon, 13 May 2019 10:05:48 -0400 Subject: [PATCH 1/2] Update content.md --- websphere-liberty/content.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/websphere-liberty/content.md b/websphere-liberty/content.md index dce742991..6806810d3 100644 --- a/websphere-liberty/content.md +++ b/websphere-liberty/content.md @@ -80,6 +80,10 @@ It is a very strong best practice to create an extending Docker image, we called If you want to build the smallest possible WebSphere Liberty application image you can start with our `kernel` tag, add your artifacts, and run `configure.sh` to grow the set of features to be fit-for-purpose. Please see our [GitHub page](https://github.com/WASdev/ci.docker#building-an-application-image) for more details. +## Enabling Enterprise functionality + +The WebSphere Liberty images have a set of built-in XML snippets that enable and configure enterprise functionality such as session cache and monitoring. These are toggled by specific `ARG`s in your application image Dockerfile and configured via the `configure.sh` script. Please the [instructions](https://github.com/wasdev/ci.docker#enterprise-functionality) on our GitHub page for more information. + ## Using volumes for configuration This pattern can be useful for quick experiments / early development (i.e. `I just want to run the application as I iterate over it`), but should not be used for development scenarios that involve different teams and environments - for these cases the `Application Image` pattern described above is the way to go. From 817d8ebf2edeee0f43c53833eef86cef5c7b935e Mon Sep 17 00:00:00 2001 From: Arthur De Magalhaes Date: Mon, 13 May 2019 20:08:42 -0400 Subject: [PATCH 2/2] Review comments Co-Authored-By: yosifkit --- websphere-liberty/content.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/websphere-liberty/content.md b/websphere-liberty/content.md index 6806810d3..0493125d6 100644 --- a/websphere-liberty/content.md +++ b/websphere-liberty/content.md @@ -82,7 +82,7 @@ If you want to build the smallest possible WebSphere Liberty application image y ## Enabling Enterprise functionality -The WebSphere Liberty images have a set of built-in XML snippets that enable and configure enterprise functionality such as session cache and monitoring. These are toggled by specific `ARG`s in your application image Dockerfile and configured via the `configure.sh` script. Please the [instructions](https://github.com/wasdev/ci.docker#enterprise-functionality) on our GitHub page for more information. +The WebSphere Liberty images have a set of built-in XML snippets that enable and configure enterprise functionality such as session cache and monitoring. These are toggled by specific `ARG`s in your application image Dockerfile and configured via the `configure.sh` script. Please see the [instructions](https://github.com/wasdev/ci.docker#enterprise-functionality) on our GitHub page for more information. ## Using volumes for configuration