[Idea] Separate configs in one file #504

New Issue

Closed

opened 2022-03-01 05:32:04 +00:00 by Firesphere · 4 comments

Firesphere commented 2022-03-01 05:32:04 +00:00

Copy Link

What I'm trying to do and why

Split backups, some repositories get everything, some only configs, etc.

Current behaviour

Borgmatic requires a configfile passed in, to run a separate or specific backup.

Other notes / implementation ideas

Currently, the YAML for configuration is flat, all repositories are in a single configuration.

My suggestion/idea, is to allow the following:

mount:
    location:
        # List of source directories to backup (required). Globs and
        # tildes are expanded. Do not backslash spaces in path names.
        source_directories:
            - /home
            - /root
        repositories:
            - /media/storage/{fqdn}
    hooks:
        et-cetera
remote:
    location:
        # List of source directories to backup (required). Globs and
        # tildes are expanded. Do not backslash spaces in path names.
        source_directories:
            - /home
            - /var/log
        repositories:
            - user@remote:{fqdn}
    hooks:
        et-cetera

With this configuration, borgmatic, without any specifications, should run all the backups (kinda like it does now)

However, if I run borgmatic -t mount, (-t is fictional, in my head it stands for "target"), it only runs the first configuration, and with -t remote, it (obviously) then only runs the second configuration.

This would give more flexibility with having multiple configurations in one place.
An shared configs would be imported just like any other yaml.

#### What I'm trying to do and why Split backups, some repositories get everything, some only configs, etc. #### Current behaviour Borgmatic requires a configfile passed in, to run a separate or specific backup. #### Other notes / implementation ideas Currently, the YAML for configuration is flat, all repositories are in a single configuration. My suggestion/idea, is to allow the following: ``` mount: location: # List of source directories to backup (required). Globs and # tildes are expanded. Do not backslash spaces in path names. source_directories: - /home - /root repositories: - /media/storage/{fqdn} hooks: et-cetera remote: location: # List of source directories to backup (required). Globs and # tildes are expanded. Do not backslash spaces in path names. source_directories: - /home - /var/log repositories: - user@remote:{fqdn} hooks: et-cetera ``` With this configuration, borgmatic, without any specifications, should run all the backups (kinda like it does now) However, if I run `borgmatic -t mount`, (-t is fictional, in my head it stands for "target"), it only runs the first configuration, and with `-t remote`, it (obviously) then only runs the second configuration. This would give more flexibility with having multiple configurations in one place. An shared configs would be imported just like any other yaml.

witten commented 2022-03-01 05:37:22 +00:00

Owner

Copy Link

Interesting! What's the benefit of this approach over the existing support for separate configuration files? For instance, if you put a mount.yaml and a separate remote.yaml in /etc/borgmatic.d, you can run them both by invoking borgmatic.. or target one of them individually with, e.g. borgmatic --config /etc/borgmatic.d/mount.yaml.

Is it just that the -t approach is easier to type at the command-line?

Interesting! What's the benefit of this approach over the existing support for separate configuration files? For instance, if you put a `mount.yaml` and a separate `remote.yaml` in `/etc/borgmatic.d`, you can run them both by invoking `borgmatic`.. or target one of them individually with, e.g. `borgmatic --config /etc/borgmatic.d/mount.yaml`. Is it just that the `-t` approach is easier to type at the command-line?

Firesphere commented 2022-03-01 06:30:19 +00:00

Author

Copy Link

Besides the import, which would make life easier...

I hadn't seen documentation where it said that /etc/borgmatic.d/name.yaml would work, from the docs I understood it had to be /etc/borgmatic/config.yaml. Did I overlook something?

Because then, my only reason would be that it's nice inside a single file, to more easily edit.

Besides the import, which would make life easier... I hadn't seen documentation where it said that `/etc/borgmatic.d/name.yaml` would work, from the docs I understood it had to be `/etc/borgmatic/config.yaml`. Did I overlook something? Because then, my only reason would be that it's nice inside a single file, to more easily edit.

witten commented 2022-03-01 06:38:09 +00:00

Owner

Copy Link

The documentation covering that is in this how-to guide. Based on that, let me know if you think that'd work for your use case. I hear you about editing in a single file being more convenient though.

The documentation covering that is in [this how-to guide](https://torsion.org/borgmatic/docs/how-to/make-per-application-backups/). Based on that, let me know if you think that'd work for your use case. I hear you about editing in a single file being more convenient though.

witten added the

waiting for response

label 2022-03-08 07:20:42 +00:00

witten commented 2022-05-20 21:46:08 +00:00

Owner

Copy Link

I'm closing this ticket due to inactivity, but if you have any follow-ups, please feel free to post them here! I'm happy to reopen if needed.

I'm closing this ticket due to inactivity, but if you have any follow-ups, please feel free to post them here! I'm happy to reopen if needed.

witten closed this issue 2022-05-20 21:46:08 +00:00

witten removed the

waiting for response

label 2022-05-20 21:46:18 +00:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

spot-check

1.8.11

1.8.10

1.8.9

1.8.8

1.8.7

1.8.6

1.8.5

1.8.4

1.8.3

1.8.2

1.8.1

1.8.0

1.7.15

1.7.14

1.7.13

1.7.12

1.7.11

1.7.10

1.7.9

1.7.8

1.7.7

1.7.6

1.7.5

1.7.4

1.7.3

1.7.2

1.7.1

1.7.0

1.6.6

1.6.5

1.6.4

1.6.3

1.6.2

1.6.1

1.6.0

1.5.24

1.5.23

1.5.22

1.5.21

1.5.20

1.5.19

1.5.18

1.5.17

1.5.16

1.5.15

1.5.14

1.5.13

1.5.12

1.5.11

1.5.10

1.5.9

1.5.8

1.5.7

1.5.7.dev0

1.5.6

1.5.5

1.5.4

1.5.3

1.5.2

1.5.1

1.5.0

1.4.22

1.4.21

1.4.20

1.4.19

1.4.18

1.4.17

1.4.16

1.4.15

1.4.14

1.4.13

1.4.12

1.4.11

1.4.10

1.4.9

1.4.8

1.4.7

1.4.6

1.4.5

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.26

1.3.25

1.3.24

1.3.23

1.3.22

1.3.21

1.3.20

1.3.19

1.3.18

1.3.17

1.3.16

1.3.15

1.3.14

1.3.13

1.3.12

1.3.11

1.3.10

1.3.9

1.3.8

1.3.7

1.3.6

1.3.5

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.18

1.2.17

1.2.16

1.2.15

1.2.14

1.2.13

1.2.12

1.2.11

1.2.10

1.2.9

1.2.8

1.2.7

1.2.6

1.2.5

1.2.4

1.2.3

1.2.2

1.2.1

1.2.0

1.1.15

1.1.14

1.1.13

1.1.12

1.1.11

1.1.10

1.1.9

1.1.7

1.1.6

1.1.5

1.1.4

1.1.3

1.1.2

1.1.1

1.1.0

1.0.3

1.0.2

1.0.1

1.0.0

0.1.8

0.1.7

0.1.6

0.1.5

0.1.4

0.1.3

0.1.2

0.1.1

0.1.0

0.0.7

0.0.6

0.0.5

0.0.4

0.0.3

0.0.2

Labels

Clear labels   

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No Label

bug

data loss

design finalized

good first issue

new feature area

question / support

security

waiting for response

Milestone

Clear milestone

No items

No Milestone

Assignees

Clear assignees

No Assignees

2 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#504

No description provided.