This is a proposal for a configuration file for restic, in TOML (see https://github.com/toml-lang/toml#example for an example).

The configuration file can be used to define global default values and aliases to repositories, which apply configuration values.

[global]

[global.backup]
exclude = [ "*.swp" ]

[gibson]
location = "sftp://gibson.domain.tld//data/backup/restic-repo"

[gibson.backup]
exclude = [ "/home/user/work", "*.go" ]
target = [ "/home/user" ]

[mainframe]
location = "sftp://mainframe.internal//home/user/repo"

[mainframe.backup]
exclude = [ "/tmp", "/proc", "/sys" ]

This leads to the following behaviour:

restic -r gibson uses sftp://gibson.domain.tld//data/backup/restic-repo as the repository location and the backup exclude list is populatated with the following patterns: *.swp, /home/user/work and *.go. If no other target is specified on the command line, restic creates a backup of /home/user.
restic -r secondary uses sftp://mainframe.internal//home/user/repo as the repository location and the backup exclude list is populatated with the following patterns: *.swp, /tmp, /proc and /sys
For every other repository location, restic works as normal, except that for the backup command *.swp is added to any other excludes defined on the command line

So if I have a good config file, creating a backup is a matter of running restic -r gibson backup. :)

Thoughts? @fw42 @scoddy

Configuration File #16

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions