mirage-config 1.0.0

Mirage Config

Version 1.0.0 Copyright 2022 Mike Bierlee Licensed under the terms of the MIT license - See LICENSE.txt

Toolkit for loading and using application configuration from various formats.

Features:

• Load from various file formats such as JSON, INI and Java properties (see Formats);
• Environment variable substitution;
• Internal configuration substitution (Value in config replaced by other path in config);
• Parse configuration from string or JSONValue instead of from disk.

Getting started

DUB Dependency

See the DUB project page for instructions on how to include Mirage Config into your project.

Quickstart

import std.stdio : writeln;
import mirage : loadConfig, parseJavaProperties;

void main() {
    // Load configuration from file (see examples/quickstart/config.json)
    auto config = loadConfig("config.json");
    writeln(config.get("application.name"));
    writeln(config.get!long("application.version"));

    // Or parse directly from string
    auto ini = parseIniConfig("
        databaseDriver = Postgres

        [database]
        host = localhost
        port = 5432
    ");

    auto databaseConfig = ini.getConfig("database");

    writeln(ini.get("databaseDriver"));
    writeln(databaseConfig.get("host"));
    writeln(databaseConfig.get("port"));
}

More formats are available (see Formats.) For more details and examples, see the examples directory.

Formats

The following file formats are currently supported:

^* Any loader or parser can be imported from the `mirage` package since they are all publicly imported. ^** Loads files based on their extension. If the file does not use one of the extensions in the table, you must use a specific loader. ^*** Besides parsing strings like the other formats, it also accepts a `JSONValue`.

Documentation

You can generate documentation from the source code using DUB:

dub build --build=ddox

The documentation can then be found in docs/

History

For a full overview of changes, see CHANGES.md

Contributing

Any and all pull requests are welcome! If you (only) want discuss changes before making them, feel free to open an Issue on github. Please develop your changes on (a branch based on) the develop branch. Continuous integration is preferred so feature branches are not neccessary.