Specify the number of copies I want for files in that repo. With that out of the way, here's some things that Git Annex lets me do: The Special Remotes support encryption using GPG. I have used the S3 remote once, but most of my experience is with data on external drives. Git Annex supports things like S3 and RClone via "Special Remotes". I use Git annex manually through command line and not through their assistant - which looks good, but I want manual control. I also have a lot of experience with Git, so I find the fact that it builds on Git as a strength, and not a source of additional complexity. This is because most of my data that is constantly change is either my own notes or my code which is plain text and managed via Git. Git Annex handles renames and moves like a champ, but editing the content requires an unlock/lock workflow that I don't have too much experience with. For example: music files (once tags have been fixed to the way i like it), tv shows, movies, ebooks, even personal documents like statements and the like. I only use it on data that is write once read many. I do not know what the experience on a Windows / Mac is like. I just use the package provided by my distro (Fedora). I run linux on my laptops and desktops and have had a great experience. I have been using it for almost 4 years now, and I intend to expand its usage to cover even more of my data. So how does the new developer know how to define the annexation.I use Git-Annex to manage nearly 18 TB of data, and I find it to be extremely well designed and reliable - both traits that I look for in a storage management system. # 38e67e39-7dfb-45e8-90fc-8c5d01aae0b4 - annexation.dirĭev2$ git annex enableremote annexation.dir directory=? The steps would be: dev1$ git clone & cd myprojectĭev1$ mkdir images & touch images/foo1.pngĭev1$ git annex initremote annexation.dir directory=/mnt/media/myproject.annex/ encrypted=falseĭev1$ git commit & git push & git annex sync -content Is there any way to glean this information from the source repo itself? * Dev 2 comes along (or Dev 1 comes along months later with a different machine) and clones the repo, but needs to know the directory=/path. * Dev 1 performs an initremote annexed-media directory=/path/to/media. Is there a way to determine the parameters that an enableremote command must use, if one does not know it? The use case is as follows: Joey Hess Automatically converted into a man page by mdwn2man. Most options are not prefixed by a dash, and set parameters of the remote,Īlso, the git-annex-common-options(1) can be used. Has found didn't work before and gave up on using, setting (This command also can be used to enable a git remote that git-annex This works best when the special remote does not need anything special Then when git-annex-init(1) is run inĪ 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, Make little sense except in cases like the revoked key example above. Keyid+= and keyid-= with such remotes should be used with care, and On files that have already been copied to the remote. One use-case of keyid-= is to replace a revoked key withĪ new key: git annex enableremote mys3 keyid-=revokedkey keyid+=newkeyĪlso, note that for encrypted special remotes using plain public-keyĮncryption (encryption=pubkey), adding or removing a key has NO effect (which is by design impossible, short of deleting the remote). However, note that removing a keyĭoes NOT necessarily prevent the key's owner from accessing data These respectivelyĪdd and remove keys from the list. The GPG keys that an encrypted special remote is encrypted with can beĬhanged using the keyid+= and keyid-= parameters. The as the encryption scheme cannot be changed once a special remote Special remote, by specifying new values for parameters that are This command can also be used to modify the configuration of an existing For example, the directory special remote requires aĭirectory= parameter every time. Some types of special remotes need parameters to be specified every time Or you can specify the uuid or description of the Git annex enableremote without any name to get a list of Setting up that remote with git annex initremote. When enabling a remote, specify the same name used when originally That was set up earlier by git annex initremote run in Git annex enableremote name|uuid|desc DESCRIPTIONĮnables use of an existing remote in the current repository, Git-annex enableremote - enables git-annex to use a remote SYNOPSIS
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |