Best practice for overriding default config properties?

[toomanyedwards <to...@gmail.com>]

Hi all,
  I'm relatively new to karaf and am looking for the best practice for
overriding karaf's default config properties (e.g. - logging, web port,
etc.).  What I'd like to be able to do is to keep my custom config property
files in a folder that does *not* live under the karaf installation.  That
way I could keep the karaf install image as is and point it to my custom
properties files to override the defaults.  Ideally, this would be able to
be done by setting a well known environment variable (e.g. -
CUSTOM_CONFIG_DIR) so that to use custom properties no change to the karaf
install would need to be made. I'd just need to set the CUSTOM_CONFIG_DIR
environment property or some such before startinf karaf.
  Soooo, my questions are: Is this possible today?  If not, what is the best
practice for managing custom config properties files? The best I can figure
is that I could modify 
${includes} in custom.properties to point to my custom properties files
outside of the karaf config, but even that would require modifying the the
karaf install (ie. - the custom.properties file).
  Any pointers to best practice are greatly appreciated. Thanks!


-edward 



--
View this message in context: http://karaf.922171.n3.nabble.com/Best-practice-for-overriding-default-config-properties-tp4028618.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Re: Best practice for overriding default config properties?

[Achim Nierbeck <bc...@googlemail.com>]

Hi,

well, it depends on which kind of configurations you want to change.
All of the *.cfg files are used by the configuration admin service and
therefore it's not possible to have two of the same configuration files.
For most of the other configuration properties your able to define your
custom properties in the custom.property file.
So you might be interested in changing the folder for those *.cfg files,
for this you need to alter the config.properies file and change the file
install location.
The current setting is set to the following:

#
# FileMonitor properties
#
felix.fileinstall.dir    = ${karaf.base}/etc
felix.fileinstall.filter = .*\\.cfg
felix.fileinstall.poll   = 1000
felix.fileinstall.noInitialDelay = true
felix.fileinstall.log.level = 3


regards, Achim


2013/5/9 toomanyedwards <to...@gmail.com>

> Hi all,
>   I'm relatively new to karaf and am looking for the best practice for
> overriding karaf's default config properties (e.g. - logging, web port,
> etc.).  What I'd like to be able to do is to keep my custom config property
> files in a folder that does *not* live under the karaf installation.  That
> way I could keep the karaf install image as is and point it to my custom
> properties files to override the defaults.  Ideally, this would be able to
> be done by setting a well known environment variable (e.g. -
> CUSTOM_CONFIG_DIR) so that to use custom properties no change to the karaf
> install would need to be made. I'd just need to set the CUSTOM_CONFIG_DIR
> environment property or some such before startinf karaf.
>   Soooo, my questions are: Is this possible today?  If not, what is the
> best
> practice for managing custom config properties files? The best I can figure
> is that I could modify
> ${includes} in custom.properties to point to my custom properties files
> outside of the karaf config, but even that would require modifying the the
> karaf install (ie. - the custom.properties file).
>   Any pointers to best practice are greatly appreciated. Thanks!
>
>
> -edward
>
>
>
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/Best-practice-for-overriding-default-config-properties-tp4028618.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>



-- 

Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home>
Commiter & Project Lead
blog <http://notizblog.nierbeck.de/>