xcgd/confnest repository overview

⁠Overview

confnest allows to manage configuration histories that let you update your application configuration or dependancies in a reliable and reproducible way.

The configurations that are entirely made of tags are called baselines⁠. The point of baseline maintenance is the ability to reproduce deliverable states. By also accepting arbitrary changesets, one can record the construction history of a baseline and exchange intermediate steps.

This tool was directy inspired by confman⁠

⁠Example

Imagine you have the following yaml configuration file named nest.yaml in a repository

repos:
  irtweaks:
    layout: src/irtweaks
    pulluri: https://bitbucket.org/xcg/irtweaks
    kind: hg
    tracktype: tag
    track: TAG_1.1
  auth_saml:
    layout: src/auth_saml
    pulluri: https://bitbucket.org/xcg/auth_saml
    kind: hg
    tracktype: tag
    track: TAG_2.1
  cobra:
    layout: src/cobra
    pulluri: https://github.com/spf13/cobra
    kind: git
    tracktype: branch
    track: master

running the command:

> confnest ensureconf

in the same directory as your config file (nest.yaml) will clone/pull/update the 3 defined repositories

Do not use any dot character (".") in the repository names, or you will get a crash from confnest.

⁠Reminder

You should version your configuration file in whatever DVCS you want and pull the desired version to your machine. This is your own configuration history that provides the baseline :)

⁠Licence

This program is provided under the MIT licence.