What about having a ~/.config/borgmatic.d/ config dir #274

New Issue

Closed

opened 2019-12-28 13:04:46 +00:00 by codingforfun · 5 comments

codingforfun commented 2019-12-28 13:04:46 +00:00

Copy Link

What I'm trying to do and why

I try to use the per app config approach running borgmatic from my user account.
I would like to use the approach of having different borgmatic configs for different sources within my home dir (e.g. work, private, music collection, pictures), to have different settings (e.g. retention).

I don’t need to backup something from the system but only from within my users home, so I would like to keep everything local to the user account and not mess around with /etc.

My scenario is to manually trigger pre-configured backups onto USB disks by just calling borgmatic.

Actual behavior

I just tried creating ~/.config/borgmatic.d/ but it’s not recognized.
Borgmatic complains with:

/etc/borgmatic/config.yaml /etc/borgmatic.d /home/<myusername>/.config/borgmatic/config.yaml: No configuration files found

Expected behavior

Would be nice if borgmatic could search config in ~/.config/borgmatic.d/ and treat it the same way as /etc/borgmatic.d.

Environment

borgmatic version: 1.3.5

borgmatic installation method: standalone binary from TGZ

Borg version: 1.1.10

Python version: 3.5.2

operating system and version: Ubuntu 16.04 LTS

#### What I'm trying to do and why I try to use the per app config approach running borgmatic from my user account. I would like to use the approach of having different borgmatic configs for different sources within my home dir (e.g. work, private, music collection, pictures), to have different settings (e.g. retention). I don’t need to backup something from the system but only from within my users home, so I would like to keep everything local to the user account and not mess around with `/etc`. My scenario is to manually trigger pre-configured backups onto USB disks by just calling `borgmatic`. #### Actual behavior I just tried creating `~/.config/borgmatic.d/` but it’s not recognized. Borgmatic complains with: ``` /etc/borgmatic/config.yaml /etc/borgmatic.d /home/<myusername>/.config/borgmatic/config.yaml: No configuration files found ``` #### Expected behavior Would be nice if borgmatic could search config in `~/.config/borgmatic.d/` and treat it the same way as `/etc/borgmatic.d`. #### Environment **borgmatic version:** 1.3.5 **borgmatic installation method:** standalone binary from TGZ **Borg version:** 1.1.10 **Python version:** 3.5.2 **operating system and version:** Ubuntu 16.04 LTS

witten commented 2019-12-28 21:54:07 +00:00

Owner

Copy Link

This makes sense to me, and should be easy to add. Thanks for suggesting it! In the meantime, if you'd like to accomplish the same thing with the version of borgmatic you're already using, you should be able to do this with:

borgmatic --config ~/.config/borgmatic.d/ ...

This makes sense to me, and should be easy to add. Thanks for suggesting it! In the meantime, if you'd like to accomplish the same thing with the version of borgmatic you're already using, you should be able to do this with: ```bash borgmatic --config ~/.config/borgmatic.d/ ... ```

witten added the

design finalized

label 2019-12-28 21:54:18 +00:00

codingforfun commented 2019-12-30 09:47:54 +00:00

Author

Copy Link

Ok. Thanks.

Ok. Thanks.

witten referenced this issue from a commit 2020-01-22 17:31:11 +00:00

Add ~/.config/borgmatic.d as another configuration directory default (#274).

witten commented 2020-01-22 17:32:16 +00:00

Owner

Copy Link

Implemented in master!

Implemented in master!

witten closed this issue 2020-01-22 17:32:16 +00:00

codingforfun commented 2020-01-22 17:39:07 +00:00

Author

Copy Link

Great! Thx.

Great! Thx.

witten commented 2020-01-27 23:42:36 +00:00

Owner

Copy Link

Released in borgmatic 1.5.0!

Released in borgmatic 1.5.0!

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

spot-check

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#274

No description provided.