Skip to content

Configuration files are too complicated, allow inclusion of shared configuration definitions. #1

@adixon

Description

@adixon

There's a fair amount of duplication and complexity in the json configuration files, maybe we could have some kind of abstraction via extra configuration files, that combine and name common shared sets.

For example, for CiviCRM file backups, it'd be nice to combine the collection of configurations that determine which directories the files live in and the exclusions, so that I can reuse that collection across multiple configuration files and modify it in a single place.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions