-
Notifications
You must be signed in to change notification settings - Fork 111
Soichi Hayashi edited this page Apr 5, 2021
·
3 revisions
Use git annex wanted
to specify the rule/selection of files. E.g. with
git annex wanted datalad-public "not metadata=distribution-restrictions=*"
datalad will transfer (by default) to datalad-public
all annexed files which do not have a git-annex metadata key distribution-restrictions
with any value.
It is possible to add another remote as a dependency for another one. E.g. with
datalad siblings -s origin --publish-depends datalad-public configure
if current branch is tracking origin
, datalad will first publish to datalad-public
remote (e.g., to upload all data files ) and only then to origin
.
Often, e.g. in case of remote servers and automated crawling etc, it is desired to store credentials while relying solely on filesystem level protection. For that purpose, create ~/.config/python_keyring/keyringrc.cfg
with
[backend]
default-keyring=keyrings.alt.file.PlaintextKeyring
and chmod go-rwx -R ~/.local/share/python_keyring/