/etc/borgmatic/config.yaml is required even when /etc/borgmatic.d/* configs are present #40
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#40
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I did this:
sudo mkdir /etc/borgmatic.d
sudo generate-borgmatic-config --destination /etc/borgmatic.d/app1.yaml
sudo generate-borgmatic-config --destination /etc/borgmatic.d/app2.yaml
sudo borgmatic
[Errno 2] No such file or directory: '/etc/borgmatic/config.yaml'
so it still only looks for config.yaml
Or are you supposed to have both a config.yaml and any additional ones in borgmatic.d? If so then you'd probably want to clarify in the docs.
Imported from Taiga issue 39 (done). Created on 2017-09-08T13:38:37+0000 by asdfasdfoaijsdf.
This isn't by design.. Just an oversight. Thanks for reporting!
Comment on 2017-09-09T04:03:06+0000 by Dan Helfman.
Fixed in borgmatic 1.1.8, just released!
Comment on 2017-09-09T04:26:32+0000 by Dan Helfman.
awesome!
Comment on 2017-09-09T10:56:41+0000 by asdfasdfoaijsdf.