This chapter covers the following topic:
Customizing DAPS behavior with a local configuration file
DAPS can be customized to a large degree: per system, per user, and per
document. The configuration file /etc/daps/config
lists all parameters that can
be configured, including a short description for each parameter. Parameters
are always defined as KEY="VALUE"
pairs. Any parameter can be
set in various locations, which are listed below in ascending order with
regard to their hierarchy. If conflicting values are set for the same parameter,
the value defined in the next higher hierarchy level takes precedence. Values
defined on the command line always take precedence over values set in any other
locations.
/etc/daps/config
(system-wide configuration file)
~/.config/daps/dapsrc
(user-specific configuration file)
DC (doc config) file of the documentation project (for settings specific to a document or documentation set)
on the fly at the command line by specifying options to a
daps
command.
For adjusting a few parameters that you want to set to custom values, do
not edit the system-wide DAPS configuration
file. Instead, check if the file ~/.config/daps/dapsrc
already exists. If not,
create the file and modify it as described below:
Open both ~/.config/daps/dapsrc
and /etc/daps/config
in a text editor.
Select which parameters you want to modify.
Copy only those to ~/.config/daps/dapsrc
.
Copying all parameters from /etc/daps/config
to
~/.config/daps/dapsrc
increases the risk of parameter incompatibilities when
you update to a higher DAPS version. As the settings in the custom
DAPS configuration file will override the settings in /etc/daps/config
by default, any parameter incompatibilities between the files may lead to
unexpected behavior of DAPS.
Save ~/.config/daps/dapsrc
and test if your changes produce the expected
results.
For a list of all parameters including a short description of each
parameter, see /etc/daps/config
in your installed system or https://github.com/openSUSE/daps/blob/main/etc/config.in.