February 22, 2015 at 6:53 pm #3164Brad TumyParticipant
By default the CLI tool uses the configuration found in /openidm/conf … if we are using another configuration directory (e.g. /openidm/acme/conf ) is it possible to have the CLI tool use this conf directory instead of the default? Specifically I am wanting to use the validate tool to validate the files found in the acme directory instead of the default conf.
One work-around would be to copy all of the customer’s customizations to the default conf directory but we would prefer keeping the customizations in a separate folder to ease the deployment and possibly recovery process.
BradFebruary 23, 2015 at 2:30 am #3167Mike JangSpectator
I assume you’re familiar with the samples in the /path/to/openidm/samples directory. I think each sample in that folder includes a conf subdirectory.
For example, when you start OpenIDM with the files associated with Sample 1 e.g. ./startup.sh -p samples/sample1, OpenIDM uses the configuration files in the samples/sample1/conf subdirectory.
(OpenIDM would then also use files from the included data and script subdirectories)
MikeFebruary 23, 2015 at 2:36 am #3168Brad TumyParticipant
Thanks for your response Mike. I understand OpenIDM will use the conf under the project folder (specified with the -p) but the ./cli.sh (or .bat) seem to still default to the conf in the root OpenIDM folder.February 23, 2015 at 10:23 am #3169
You must be logged in to reply to this topic.