![]() ![]() It knows about the remote, but hasn't assigned a name to it: 11:53:36 git annex info glacier (merging origin/git-annex into git-annex.) I then did a git clone from the bare repo into a tmp dir: 11:52:48 git clone /media/craig/KINGSTON/annex-pics annex-picsīut when I enable the glacier remote, which I'd have to do in a DR scenario, I get an error: 11:53:29 git annex enableremote glacier 11:50:50 pwdĪnnex branches config description HEAD hooks info objects refs This created a annex-pics directory on the usb key with a bare repo. I used git annex assistant to create a manual mode remote on my usb key. Uuid: e34c5f10-2a97-4477-a248-b96e050557dcĮncryption: encrypted (encryption key stored in git repository) My main repo is ~/local/pics and here's the result of git annex info glacier: 11:45:24 git annex info glacier However, I seem to be missing something with enableremote and how this is all supposed to work. I'm now sure I could recover my data in a DR scenario. I see the gpg key in remote.log in the git-annex branch, so it's saved, which is the thing I care about most. Special remotes don't support removal of uploaded files, so be carefulĬool, thanks. Remote it won't touch your existing files stored on the remote.įor most remotes, it also won't bloat the remote with any data, since It's safe to use this command even when you're already storing data in a It tests the -size parameter can adjust it to test using smaller files. Particularly useful to test new implementations of special remotes.īy default it will upload and download files of around 1MiB to the remote This expects you to have set up the remoteĪs usual, and it then runs a lot of tests, using random data. To make sure that a special remote is working correctly, you can use the (To remove unwanted data: git-annex dropunused -from mys3 NUMBER) (To see where data was previously used, try: git log -stat -S'KEY') Some annexed data on mys3 is not used by any files in this repository. On special remotes, instead use git annex unused -from. Repository is found by running git annex unused. ![]() Over time, special remotes can accumulate file content that is no longer ![]() It largelyĭoesn't matter for your use what underlying transport the special remote Most special remotes can all be used in these and other ways. None of these use cases are particular to particular special remote types. To drop files from the transfer repository once they have been transferred Last scenario, which is referred to as a transfer repository, and arranges The git-annex assistant makes it easy to set up rsync remotes using this Remote, and then git annex get them on another repository, to transfer theįiles between computers that do not communicate directly. You could have one repository copy files to a special Getting full, and then git annex move the files back when free space isĪgain available. Git annex move -to specialremote large files when your local drive is You could use it to archive files offline in a drive withĮncryption enabled so if the drive is stolen your data is not. There are many use cases for a special remote. Want to add support for something else? Write your own! Ways to use special remotes If a service is not mentioned above, it's worth checking if Openstack Swift / Rackspace cloud files / Memset Memstore.Here are specific instructions for using git-annex with various services: To tie git-annex into many cloud services. The above special remotes are built into git-annex, and can be used S3 (Amazon S3, and other compatible services).They cannot be used by other git commands, and These can be used by git-annex to store and retrieve Local and remote), that store the file contents in their own git-annexīut, git-annex also extends git's concept of remotes, with these special Normally those remotes are normal git repositories (bare and non-bare Git-annex can transfer data to and from configured git remotes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |