relconf

Manage configuration depending to the current path

relconf generates toml, yaml and configuration files based on the current path. It reads its configuration from a yaml file (see Usage for where that file is expected to be), merges toml/yaml/json files based on the current path, writes the final configuration to disk and optionally outputs an environment variable pointing to the generated config.

Table of Contents

• Install
• Usage
• Publishing relconf
• Maintainers
• Contributing
• License

Install

You can download the correct version for your operating system and architecture using the download.ps1 script. Don't let the name fool you, the script works with Bash/ZSH on Linux or macOS too!

On Linux or macOS run:

curl -s https://raw.githubusercontent.com/kfkonrad/relconf/main/download.ps1 | bash
# OR
wget -qO- https://raw.githubusercontent.com/kfkonrad/relconf/main/download.ps1 | bash

On Windows run:

Invoke-Expression ((Invoke-WebRequest -Uri "https://raw.githubusercontent.com/kfkonrad/relconf/main/download.ps1").Content)

If you don't like running scripts from the internet you can find and download the application in the releases section of this repo as well.

You can also install from source using cargo:

cargo install relconf

Usage

# generate configs for all tools
relconf
# generate configs only for listed tools
relconf -o foo,bar

relconf in practice

Relconf will not run automatically. I recommend writing a wrapper around tools that use relconf to manage their configuration like so and adding the wrapper to your .bashrc/.zshrc/config.fish (or similar).

• Bash/ZSH:

  # as an alias
  alias foo="source <(relconf -o foo); command foo"
  # or as a function
  function foo() {
    source <(relconf -o foo)
    command foo $@
  }
  

• Fish:

  function foo --wraps foo
    relconf -o foo | source
    command foo $argv
  end
  

Set up like this relconf will always run before the command foo gets executed, ensuring the configuration is current and appropriate for whatever directory you're running foo in.

relconf's config file

relconf reads its configuration from disk. The following is an example configuration that uses all features.

tools:
- name: jj
  format: toml # or yaml or json
  rootconfig: ~/.jjconfig.toml # mandatory
  inject:
    - env-name: JJ_CONFIG # optional
      path: ~/.config/jj/merged.toml
    - path: ~/.config/jj/other-location.toml
  subconfigs:
    - path: ~/.config/jj/always.toml
    - path: ~/.config/jj/company.toml
      when: # optional, when absent the subconfig will always be imported
        - directory: ~/workspace/company-gitlab
          match-subdirectories: true # optional, defaults to false

relconf preserves the order in which subconfigs are listed and will merge and overwrite values in that order as well.

If an injection has the env-name key set relconf will output something like this (based on the above config):

export JJ_CONFIG=/home/USERNAME/.config/jj/merged.toml

The output to stdout made by relconf is safe to source in Bash, ZSH (and other posix compatible shells) and Fish. This makes it easy to automatically set the appropriate configuration variable like the snippets in the section above do.

There's also a JSON Schema for the relconf config format available in /assets/relconf.schema.json.

Config file location

The default location for the config file depends on your operating system. See the table below for an overview. Note that only Linux, macOS and Windows are supported.

You can override the default location by setting RELCONF_CONFIG or by using relconf -c path/to/config.yaml.

generting the schema

To generate the schema, relconf needs to be built with the schema feature enabled. You can enable the feature and generate the schema like so:

cargo run -F schema -- --generate-schema

Publishing relconf

See the documentation of kfkonrad/generator-standard-readme-rust on how publishing relconf works. Both repos use the same mechanism and scripts.

Maintainers

@kfkonrad

Contributing

PRs accepted.

Small note: If editing the README, please conform to the standard-readme specification.

License

MIT © 2024 Kevin F. Konrad