Support for initializing repositories #110
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#110
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?
Please include support for
borg init
, the only command I need to do manually outside of borgmatic.Interesting idea! How would you envision the specifics of this initialization? For instance, maybe you would create a borgmatic configuration as per usual, and then run something like:
And it would implicitly use the repository path specified in the borgmatic config, and pass that along to
borg init
?Something along those lines? Another other requirements you have in mind?
borgmatic --init --encryption=repokey
look good to me.Another idea was that when
bormatic --create
doesn't find an iniitlized repo on the first run it could ask if it should inititialise it (and ask for encryption mode i.e.).But i'd be super fine with an manual call of
borgmatic --init --encryption=repokey
as start.Just released as part of borgmatic 1.2.12! Let me know how it works out for you.
@witten: Thx !
Cool, thanks. My only concern with automatic initialization (with or without a prompt) is that it might not be desired behavior in certain circumstances, e.g. when not run in interactive mode. I'm thinking when you're running
borgmatic --create
from a cron job, which is pretty common.Anyway, I'll assume the explicit
borgmatic --init
approach for starters.