local bup remotes
This commit is contained in:
parent
939c88787a
commit
5d7ef05d95
2 changed files with 8 additions and 2 deletions
|
@ -22,8 +22,8 @@ These parameters can be passed to `git annex initremote` to configure bup:
|
|||
the new key id.
|
||||
|
||||
* `remote` - Required. This is passed to `bup` as the `--remote`
|
||||
to use to store data. `bup init` will be run to create the
|
||||
repository. Example: "remote=example.com:/big/mybup"
|
||||
to use to store data. To create the repository,`bup init` will be run.
|
||||
Example: "remote=example.com:/big/mybup" or "remote=/big/mybup"
|
||||
|
||||
Options to pass to `bup split` when sending content to bup can also
|
||||
be specified, by using `git config annex.bup-split-options`. This
|
||||
|
|
|
@ -5,6 +5,12 @@ git-annex, you can have git on both the frontend and the backend.
|
|||
|
||||
Here's how to create a bup remote, and describe it.
|
||||
|
||||
[[!template id=note test="""
|
||||
Instead of specifying a remote system, you could choose to make a bup
|
||||
remote that is only accessible on the current system, by passing
|
||||
"remote=/big/mybup".
|
||||
"""]
|
||||
|
||||
# git annex initremote mybup type=bup encryption=none remote=example.com:/big/mybup
|
||||
initremote bup (bup init)
|
||||
Initialized empty Git repository in /big/mybup/
|
||||
|
|
Loading…
Add table
Reference in a new issue