toremoving.blogg.se

Move unused files to trash remote git annex unused Start web console git-annex webapp -config web.browser=google-chrome-stable \ Git-annex assistant -autostart -notify-start -notify-finish

git config remote.annex-ignore true – prevents git-annex from storing (syncing) file contents on this remote by default (–from and –to options still work).git config remote.annex-cost-command – the command is run, and the number it outputs is used as the cost.git config remote.annex-cost – sets cost of annexed files transfers, repos with lower costs are preferred (defaults are 100 for local repositories and 200 for remote repositories).git annex untrust – the repository is not trusted and could lose content at any time.git annex trust – the repository is trusted to not unexpectedly lose content.git annex schedule – gets/sets scheduled jobs (expression is “fsck self” or “fsck UUID” action, where UUID is the UUID of a remote to fsck, followed by the duration to allow the action to run, and finally the schedule of when to run it).git annex group – adds the repository to a group (e.g., into one of standard groups).git annex wanted – gets/sets preferred content expression in this repository.git annex describe – changes the description of the repository.|| ( mkdir git-annex & git -git-dir=git-annex init ) Notes on Synchronization and Backup of $HOME using git, git-annex and mr.Keep the repository up to date automatically.Version 6 (locked and unlocked files, annex.thin).Enable synchronization requests via Jabber/XMPP.Set an encrypted SSH remote bare Git repository as a backup storage.(This command also can be used to enable a git remote that git-annex has found didn’t work before and gave up on using, setting remote.annex−ignore. Of course, this works best when the special remote does not need anything special to be done to get it enabled. Then when git-annex− init(1) is run in a new clone, it will will attempt to enable the special remote. If you get tired of manually enabling a special remote in each new clone, you can pass "autoenable=true". Hence using keyid+= and keyid−= with such remotes should be used with care, and make little sense except in cases like the revoked key example above. Git annex enableremote mys3 keyid−=revokedkey keyid+=newkeyĪlso, note that for encrypted special remotes using plain public−key encryption (encryption=pubkey), adding or removing a key has NO effect on files that have already been copied to the remote. One use−case of keyid−= is to replace a revoked key with a new key: However, note that removing a key does NOT necessarily prevent the key’s owner from accessing data in the encrypted special remote (which is by design impossible, short of deleting the remote).

These respectively add and remove keys from the list. The GPG keys that an encrypted special remote is encrypted with can be changed using the keyid+= and keyid−= parameters. (However, some settings such as the as the encryption scheme cannot be changed once a special remote has been created.)

This command can also be used to modify the configuration of an existing special remote, by specifying new values for parameters that are usually set when using initremote. The command will prompt for any required parameters you leave out. For example, the directory special remote requires a directory= parameter every time. Some types of special remotes need parameters to be specified every time they are enabled. Or you can specify the uuid or description of the remote.

Run git annex enableremote without any name to get a list of remote names. When enabling a remote, specify the same name used when originally setting up that remote with git annex initremote. Git annex enableremote name|uuid|desc DESCRIPTIONĮnables use of an existing remote in the current repository, that was set up earlier by git annex initremote run in another clone of the repository. Git-annex-enableremote − enables git-annex to use a remote SYNOPSIS