BES Configuration File

From OPeNDAP Documentation
Revision as of 04:51, 1 October 2009 by PatrickWest (talk | contribs) (New page: == Current Problem == Current, any modules that the BES loads adds information to the one BES configuration file. This causes problems in many scenarios. * Development work where you have ...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

1 Current Problem

Current, any modules that the BES loads adds information to the one BES configuration file. This causes problems in many scenarios.

  • Development work where you have to do a 'make install' many times, which over-writes the BES configuration file
  • Upgrading the BES, the install over-writes the configuration file

2 Suggested Solution

  1. The BES configuration file holds only the information for the BES, no loaded modules
  2. Add new keywords in the configuration file to include other configuration files, like what Apache HTTPD does
    • include conf.d/*.conf - we would do something similar to this
    • allow regular expression matching of files
    • allow for a direct include
    • allow multiple includes
    • recommend that they leave the include line alone, and rename conf files if they don't want them installed (like with Apache HTTPD)
    • Modify the behavior for BES.modules, or have a new keyword like "Add BES.modules", or BES.addModules=nc and keep the BES.nc.module=<path_to_so>
  3. When doing an install, don't install a new configuration file, but update the one that is there, if need be. Same with the install target to make, only make changes that need to be made.
    • Perhaps a script that gets run to update the BES configuration file with any changes needed