Support for initializing repositories #110

New issue

Closed

opened 2018-11-19 22:08:10 +00:00 by varac · 5 comments

varac commented 2018-11-19 22:08:10 +00:00

Copy link

Please include support for borg init, the only command I need to do manually outside of borgmatic.

Please include support for `borg init`, the only command I need to do manually outside of borgmatic.

witten commented 2018-11-20 21:39:51 +00:00

Owner

Copy link

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:

borgmatic --init --encryption=repokey

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?

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: ```bash borgmatic --init --encryption=repokey ``` 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?

varac commented 2018-11-20 22:27:41 +00:00

Author

Copy link

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.

`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.

witten referenced this issue from a commit 2018-12-11 06:24:32 +00:00

Support for Borg repository initialization via borgmatic --init command-line flag (#110).

witten commented 2018-12-11 06:29:06 +00:00

Owner

Copy link

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.

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.

witten commented 2018-12-11 06:35:31 +00:00

Owner

Copy link

Just released as part of borgmatic 1.2.12! Let me know how it works out for you.

Just released as part of borgmatic 1.2.12! Let me know how it works out for you.

witten closed this issue 2018-12-11 06:35:32 +00:00

varac commented 2018-12-11 13:23:58 +00:00

Author

Copy link

@witten: Thx !

@witten: Thx !

witten added the

design finalized

label 2036-02-07 11:53:30 +00:00

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

parallel-borgmatic

command-hook-steps

2.1.7

2.1.6

2.1.5

2.1.4

2.1.3

2.1.2

2.1.1

2.1.0

2.0.13

2.0.12

2.0.11

2.0.10

2.0.9

2.0.8

2.0.7

2.0.6

2.0.5

2.0.4

2.0.3

2.0.2

2.0.1

2.0.0

1.9.14

1.9.13

1.9.12

1.9.11

1.9.10

1.9.9

1.9.8

1.9.7

1.9.6

1.9.5

1.9.4

1.9.3

1.9.2

1.9.1

1.9.0

1.8.14

1.8.13

1.8.12

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   

blocked

  

breaking

  

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No labels

blocked

breaking

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

No description provided.