To enable an existing special remote, the new enableremote command must be used. The initremote command now is used only to create new special remotes.
This commit is contained in:
parent
9a24728d95
commit
85d83e7756
14 changed files with 141 additions and 52 deletions
|
@ -21,7 +21,7 @@ the S3 remote.
|
|||
every clone of the repository to access the encrypted data (use with caution).
|
||||
|
||||
Note that additional gpg keys can be given access to a remote by
|
||||
rerunning initremote with the new key id. See [[encryption]].
|
||||
running enableremote with the new key id. See [[encryption]].
|
||||
|
||||
* `embedcreds` - Optional. Set to "yes" embed the login credentials inside
|
||||
the git repository, which allows other clones to also access them. This is
|
||||
|
|
|
@ -26,7 +26,7 @@ These parameters can be passed to `git annex initremote` to configure bup:
|
|||
every clone of the repository to access the encrypted data (use with caution).
|
||||
|
||||
Note that additional gpg keys can be given access to a remote by
|
||||
rerunning initremote with the new key id. See [[encryption]].
|
||||
running enableremote with the new key id. See [[encryption]].
|
||||
|
||||
* `buprepo` - Required. This is passed to `bup` as the `--remote`
|
||||
to use to store data. To create the repository,`bup init` will be run.
|
||||
|
|
|
@ -16,7 +16,7 @@ remote:
|
|||
every clone of the repository to decrypt the encrypted data.
|
||||
|
||||
Note that additional gpg keys can be given access to a remote by
|
||||
rerunning initremote with the new key id. See [[encryption]].
|
||||
running enableremote with the new key id. See [[encryption]].
|
||||
|
||||
* `chunksize` - Avoid storing files larger than the specified size in the
|
||||
directory. For use on directories on mount points that have file size
|
||||
|
|
|
@ -27,7 +27,7 @@ the Glacier remote.
|
|||
every clone of the repository to access the encrypted data (use with caution).
|
||||
|
||||
Note that additional gpg keys can be given access to a remote by
|
||||
rerunning initremote with the new key id. See [[encryption]].
|
||||
running enableremote with the new key id. See [[encryption]].
|
||||
|
||||
* `embedcreds` - Optional. Set to "yes" embed the login credentials inside
|
||||
the git repository, which allows other clones to also access them. This is
|
||||
|
|
|
@ -31,7 +31,7 @@ These parameters can be passed to `git annex initremote`:
|
|||
every clone of the repository to access the encrypted data.
|
||||
|
||||
Note that additional gpg keys can be given access to a remote by
|
||||
rerunning initremote with the new key id. See [[encryption]].
|
||||
running enableremote with the new key id. See [[encryption]].
|
||||
|
||||
* `hooktype` - Required. This specifies a collection of hooks to use for
|
||||
this remote.
|
||||
|
|
|
@ -21,7 +21,7 @@ These parameters can be passed to `git annex initremote` to configure rsync:
|
|||
every clone of the repository to decrypt the encrypted data.
|
||||
|
||||
Note that additional gpg keys can be given access to a remote by
|
||||
rerunning initremote with the new key id. See [[encryption]].
|
||||
running enableremote with the new key id. See [[encryption]].
|
||||
|
||||
* `rsyncurl` - Required. This is the url or `hostname:/directory` to
|
||||
pass to rsync to tell it where to store content.
|
||||
|
@ -31,7 +31,7 @@ These parameters can be passed to `git annex initremote` to configure rsync:
|
|||
setups, but not with some hosting providers that do not expose rsynced
|
||||
filenames to the shell. You'll know you need this option if `git annex get`
|
||||
from the special remote fails with an error message containing a single
|
||||
quote (`'`) character. If that happens, you can re-run initremote
|
||||
quote (`'`) character. If that happens, you can run enableremote
|
||||
setting shellescape=no.
|
||||
|
||||
The `annex-rsync-options` git configuration setting can be used to pass
|
||||
|
|
|
@ -16,7 +16,7 @@ the webdav remote.
|
|||
every clone of the repository to access the encrypted data (use with caution).
|
||||
|
||||
Note that additional gpg keys can be given access to a remote by
|
||||
rerunning initremote with the new key id. See [[encryption]].
|
||||
running enableremote with the new key id. See [[encryption]].
|
||||
|
||||
* `embedcreds` - Optional. Set to "yes" embed the login credentials inside
|
||||
the git repository, which allows other clones to also access them. This is
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue