From f1235bf3fd9bacad0c739ae0c711fc5698635718 Mon Sep 17 00:00:00 2001 From: Stefan Seifert Date: Wed, 10 Jan 2024 13:49:19 +0100 Subject: [PATCH] add link to real world example --- src/site/markdown/osgi-config-combined-json.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/site/markdown/osgi-config-combined-json.md b/src/site/markdown/osgi-config-combined-json.md index f71585b..e409481 100644 --- a/src/site/markdown/osgi-config-combined-json.md +++ b/src/site/markdown/osgi-config-combined-json.md @@ -47,6 +47,9 @@ The following keys are allowed on toplevel of the JSON file: `runmode` can be a comma-separate strings, e.g. `prod,publish`. In this case all given run modes have to be active. On AEM as a Cloud Service, only the [officially supported run modes][aemaacs-runmodes] are allowed. +You can use comments in the JSON file, they are stripped out when generating the `.cfg.json` files. + +Real world example with HBS template: [wcm-io-samples-aem-cms-config.osgiconfig.json.hbs](https://github.com/wcm-io/io.wcm.samples/blob/develop/config-definition/src/main/templates/wcm-io-samples-aem-cms/wcm-io-samples-aem-cms-config.osgiconfig.json.hbs) [sling-provisioning]: https://sling.apache.org/documentation/development/slingstart.html [sling-repoinit]: https://sling.apache.org/documentation/bundles/repository-initialization.html