datalad create-sibling-ria2
Synopsis
datalad create-sibling-ria2 [-h] [-s NAME] [-d DATASET] [--storage-name NAME] [--alias ALIAS] [--post-update-hook] [--shared {false|true|umask|group|all|world|everybody|0xxx}] [--group GROUP] [--storage-sibling MODE] [--existing MODE] [--new-store-ok] [--trust-level TRUST-LEVEL] [-r] [-R LEVELS] [--version] ria+<ssh|file|http(s)>://<host>[/path]
Description
Creates a sibling to a dataset in a RIA store
Just a shim implementation for now
Options
ria+<ssh|file|http(s)>://<host>[/path]
URL identifying the target RIA store and access protocol.
-h, --help, --help-np
show this help message. --help-np forcefully disables the use of a pager for displaying the help message
-s NAME, --name NAME
Name of the sibling. With RECURSIVE, the same name will be used to label all the subdatasets' siblings.
-d DATASET, --dataset DATASET
specify the dataset to process. If no dataset is given, an attempt is made to identify the dataset based on the current working directory.
--storage-name NAME
Name of the storage sibling (git-annex special remote). Must not be identical to the sibling name. If not specified, defaults to the sibling name plus '-storage' suffix. If only a storage sibling is created, this setting is ignored, and the primary sibling name is used.
--alias ALIAS
Alias for the dataset in the RIA store. Add the necessary symlink so that this dataset can be cloned from the RIA store using the given ALIAS instead of its ID. With recursive=True, only the top dataset will be aliased.
--post-update-hook
Enable Git's default post-update-hook for the created sibling. This is useful when the sibling is made accessible via a "dumb server" that requires running 'git update-server-info' to let Git interact properly with it.
--group GROUP
Filesystem group for the repository. Specifying the group is crucial when --shared=group.
--storage-sibling MODE
By default, an ORA storage sibling and a Git repository sibling are created (on). Alternatively, creation of the storage sibling can be disabled (off), or a storage sibling created only and no Git sibling (only). In the latter mode, no Git installation is required on the target host. [Default: True]
--existing MODE
Action to perform, if a (storage) sibling is already configured under the given name and/or a target already exists. In this case, a dataset can be skipped ('skip'), an existing target repository be forcefully re-initialized, and the sibling (re-)configured ('reconfigure'), or the command be instructed to fail ('error'). Constraints: value must be one of ('skip', 'error', 'reconfigure') [Default: 'error']
--new-store-ok
When set, a new store will be created, if necessary. Otherwise, a sibling will only be created if the url points to an existing RIA store.
--trust-level TRUST-LEVEL
specify a trust level for the storage sibling. If not specified, the default git-annex trust level is used. 'trust' should be used with care (see the git- annex-trust man page).
-r, --recursive
if set, recurse into potential subdatasets.
-R LEVELS, --recursion-limit LEVELS
limit recursion into subdatasets to the given number of levels. Constraints: value must be convertible to type 'int' or value must be NONE
--version
show the module and its version which provides the command