Elektra

Elektra serves as a universal and secure framework to access configuration settings in a global, hierarchical key database.

Elektra provides a mature, consistent and easily comprehensible API. Its modularity effectively avoids code duplication across applications and tools concerning their configuration tasks. Elektra abstracts from cross-platform-related issues and enables applications to be aware of other applications' configurations, leveraging easy application integration.

Often Used Links

• If you are new, start reading Get Started
• If you enjoy working with docker take a look at our docker images.
• Build server
• Website
• API documentation

Overview

Elektra provides benefits for:

1. Application Developers by making it easier to access configuration settings in a modular, reliable, and extensible way.
2. System Administrators by making it possible to access configuration settings in the same way applications access them.
3. Everyone by making application integration possible and less misconfiguration a reality.

Elektra consists of three parts:

1. LibElektra is a modular configuration access toolkit to construct and integrate applications into a global, hierarchical key database. The building blocks are:
   • language bindings (inclusive high-level interfaces)
   • GenElektra, the code generator for type-safe bindings
   • plugins for configuration access behavior and validation
2. SpecElektra is a configuration specification language that is easy to use and self-contained in the same key database (i.e. written in any of the configuration file formats Elektra supports).
3. Tools on top of LibElektra for system administrators, such as CLI tools, web UIs, and GUIs.

To highlight a few concrete things about Elektra, configuration settings can come from any data source, but usually comes from configuration files that are mounted into Elektra similar to mounting a file system. Elektra is a plugin-based framework, for example, plugins implement various configuration formats like INI, JSON, XML, etc. There is a lot more to discover like executing scripts (python, lua or shell) when a configuration value changes, or, enhanced validation plugins that will not allow corrupted configuration settings to reach your application.

As an application developer you get instant access to various configuration formats and the ability to fallback to default configuration settings without having to deal with this on your own. As an system administrator you can choose your favorite configuration format and mount this configuration for the application. Mounting enables easy application integration as any application using Elektra can access any mounted configuration. You can even mount /etc files such as hosts or fstab, so that there is no need to configure the same values twice in different files.

In case you are worried about linking to such a powerful library. The core is a small library implemented in C, works cross-platform, and does not need any external dependencies. There are bindings for other languages in case C is too low-level for you.

Contact

Do not hesitate to ask any question on GitHub issue tracker or directly to one of the authors.

Quickstart

Installation

The preferred way to install Elektra is by using packages provided for your distribution, see INSTALL for available packages and alternative ways for installation.

Note: It is preferable to use a recent version: They contain many bug fixes and usability improvements.

Usage

Now that we have Elektra installed, we can start:

• using the kdb command,
• using qt-gui for people preferring graphical user interfaces, and
• using web-ui for people preferring web user interfaces.

Documentation

To get an idea of Elektra, you can take a look at the presentation.

In the GitHub repository the full documentation is available, including:

• tutorials,
• FAQ,
• glossary, and
• concepts and man pages

You can read the documentation for the kdb tool, either

• on the Website
• in the API documentation
• by using man kdb
• by using kdb --help or kdb help <command>
• on GitHub

Note: All these ways to read the documentation provide the same content, all generated from the GitHub repository.

Facts and Features

• Elektra uses simple key-value pairs.
• Elektra uses the BSD licence.
• Elektra implements an API to fully access a global key database.
• Elektra can be thought of a virtual file system for configuration.
• Elektra supports mounting of existing configuration files into a global key database.
• Elektra has dozens of Plugins that make it possible to have a tiny core, but still support many features, including:
  • Elektra can import and export configuration files in any supported format.
  • Elektra is able to log and notify other software on any configuration changes, for example, using Dbus and Journald.
  • Elektra can improve robustness by rejecting invalid configuration via type checking, regex and more.
  • Elektra provides different mechanisms to locate configuration files.
  • Elektra supports different ways to escape and encode content of configuration files.
• Elektra is multi-process safe and can be used in multi-threaded programs.
• Elektra (except for some plugins) is portable and completely written in ANSI C99.
• Elektra (except for some plugins) has no external dependency.
• Elektra is suitable for embedded systems and early boot stage programs.
• Elektra provides many powerful Bindings to avoid low-level access code.
• Elektra provides powerful Code Generation Techniques for high-level configuration access.

News

Go to the website, see the news, and its RSS feed.

Download

Elektra uses a Git repository at GitHub.

You can clone the latest version of Elektra by running:

git clone https://github.com/ElektraInitiative/libelektra.git

Releases can be downloaded from here.

Build Server

The build server builds Elektra for every pull request and on every commit in various ways and also produces LCOV code coverage report.

Contributing

Take a look at how to start contributing.

Goals

• Make developer's life easier by proving a well-tested mature library instead of rolling your own configuration system for every application. This reduces rank growth of configuration systems (including but not limited to configuration file parsers) in our ecosystem and fosters well-maintained plugins instead.
• Postpone configuration decisions (such as which configuration files to use) from developers to system administrators and package maintainers to provide an overall more consistent and user-friendly system. (Default behavior of applications still is in control of developers, you can even roll your own plugins to provide exactly the same behavior as your application has now.)
• Make configuration storage more safe: avoid that applications receive wrong or unexpected values that could lead to undefined behavior.

And in terms of quality, we want:

1. Simplicity (make configuration tasks, like access of configuration settings, simple),
2. Robustness (no undefined behavior of applications), and
3. Extensibility (gain control over configuration access)

Continue reading about the goals of Elektra