NAME¶
elektra-glossary - glossary of Elektra
Introduction¶
- Configuration
settings
- customize applications towards the users needs.
- Configuration
storage
- makes configuration settings persistent. The application will read the
configuration at every start from the configuration storage, but it is
only stored if a user changes settings.
- Key databases
- are used for configuration storages because of these constraints. They can
do fast key lookups and the keys can be structured hierarchically by
defining separators in the key names.
- Global key
database
- provides global access to all configuration storages of all applications
in a system. Abbreviated as KDB.
- LibElektra
- is a set of libraries /src/libs/ to access configuration parameters
in a global, hierarchical key database.
- SpecElektra
- is a specification language /doc/METADATA.ini that allows us to
describe the content of the global key database.
- Elektra
- is a framework consisting of LibElektra, SpecElektra, and a collection of
tools.
- To elektrify an
application
- to change the application so that it uses LibElektra afterwards.
- Elektra
Initiative
- is a community that develops LibElektra, expands SpecElektra, improves
Elektra´s tooling and helps to elektrify applications.
Details¶
- Sync Flag
elektra-sync-flag.md
- Marks keys that were changed and need to be written out to disc.
- Null Keys, Null Values
elektra-values.md
- The absence of keys or values.
- pop
- used in ksPop() and @ref KDB_O_POP means to remove a key from a
keyset.
- delete
- or abbr. del, used in keyDel(), ksDel() and @ref KDB_O_DEL
means to free a key or keyset. The memory can be used for something else
afterwards.
- remove
- means that the key-value information in the physical database will be
removed permanently.