As of DSpace 6, the old "build.properties" configuration file has been replaced by this new "local.cfg" configuration file. For individuals who are familiar with the old build.properties file, this new local.cfg differs in a few key ways: - Unlike
build.properties, the local.cfg file can be used to override ANY setting in any other configuration file (dspace.cfg or /config/modules/*.cfg). Simply To override a default setting, simply copy the setting configuration into your local.cfg and add a different valuechange its value(s). - Unlike
build.properties, the local.cfg file is actually not utilized during the compilation process (e.g. mvn package). But, it is automatically copied alongside the final dspace.cfg into your installation location ([dspace]/config/), where it overrides default DSpace settings with your locally specific settings at runtime. - Like
build.properties, the local.cfg file is expected to be specified in the source directory by default ([dspace-source]). There is an example ([dspace-source]/local.cfg.EXAMPLE) provided which you can use to create a [dspace-source]/local.cfg.- If you are using Git to checkout the DSpace code, the
[dspace-source]/local.cfg file will be ignored by default (to avoid committing your local configs to source code). But, if you wanted to store your local.cfg file in your own local copy of the source code, you can move it over into the [dspace-source]/dspace/config/local.cfg (where it won't be ignored by Git, and will still be copied into your final [dspace]/config/ installation directory)
|