This file -- not valid XML -- contains illustrative examples of the configuration
authorSebastian Hammer <quinn@indexdata.com>
Sun, 25 Mar 2007 16:06:35 +0000 (16:06 +0000)
committerSebastian Hammer <quinn@indexdata.com>
Sun, 25 Mar 2007 16:06:35 +0000 (16:06 +0000)
commit76f5b4db8be97194a9ba0c44081796304da06347
tree495f792d3f6402b295ff52f8e1909e6a2be87ef0
parentf53516031317781ebb1a92691e3999de0afa72eb
This file -- not valid XML -- contains illustrative examples of the configuration
file format I have in mind. It is basically a mechanism to allow you to set
multiple name-value pairs for targets -- possibly user specific. The various forms
are intended to support various activities -- like setting system-wide defaults,
overriding settings for one user or target, setting up values for a specific target,
etc. There's even a verbose form that would lend itself well to dumping values
out of a relational database... indeed, it's possible to imagine an extension that
would allow pazpar2 to access settings from an RDBMS, although this is not planned
at present.
etc/example-settings [new file with mode: 0644]