Page History

...

• Any setting in your local.cfg will automatically OVERRIDE a setting of the same name in the dspace.cfg or any modules/*.cfg file.  This also means that you can copy ANY configuration (from dspace.cfg or any modules/*.cfg file) into your local.cfg to specify a new value.
  
  • For example, specifying dspace.url in local.cfg will override the default value of dspace.url in dspace.cfg.
  • Also, specifying oai.solr.url in local.cfg will override the default value of oai.solr.url in config/modules/oai.cfg
• The local.cfg file is an Apache Commons Configuration Property file. For more information see the Commons Config Properties File documentation
  • This means it
  can also
  • has enhanced features like the ability to include other config files (via "include=" statements).
  For more information see the Commons Config Properties File documentation
• As needed, you also are able to OVERRIDE settings in your local.cfg by specifying them as System Properties or Environment Variables.
  • For example, if you wanted to change your dspace.dir in development/staging environment, you could specify it as a System Property (e.g. -Ddspace.dir=[new-location]). This new value will override any value in both local.cfg and dspace.cfg.

An example local.cfg is provided at [dspace-source]/local.cfg.EXAMPLE. The example only provides a few key configurations which all DSpace sites are likely to need to customize. However, you may add (or remove) any other configuration to your local.cfg to customize it as you see fit.