Then it will propagate itself, if you allowed it. You just do not need to remember about it - just move a file and it will add itself on its own, what's great.
It's very flexible and with git annex assistant or git annex webapp it's really easy to use. Git annex is kinda hard to learn for me - i mean to use it you need to spent a little of time, but to master it you need to spend around month.
#Git annex documentation Offline#
Git annex keeps 3 copies of my files + another copies on my working machines - usually i have one file online and two copies in offline storage as backups. Some stats - i have two git annex repos - first is 2 792 137 files which takes rougly 40TB, second is 83 618 464 files which takes around 75TB of space. In all those cases - git annex is a king. And there are data which i need once a year actually, but it's good to know where They are. Most of the time i do not need all data on my processing rig or my mobile laptop. I have most of my data online (inside LAN), but some are actually now.
Writing objects: 100% ( 44/44), 3.66 KiB | 0 bytes/s, done.Actually i can not agree with u/NoMoreNicksLeft - i use git annex just as my file managment tool, but i do not know it well yet. (merging corinth/git-annex into git-annex.)Ĭompressing objects: 100% ( 18/18), done. Keep track of which of my 3 external USB drives the actual photos exist 0 ~/myrepo(master)% git remote add corinth 0 ~/myrepo(master)% git annex syncĠabc238.9a23674 git-annex -> usbdrive/git-annex Keep the folder hierarchy for every photo I've ever taken, but without having to Gigabytes of photos that will definitely not fit on my laptop's SSD, so I can This is where I really get a lot of value out of git-annex, I have about 40 You would expect because all of the information metadata is stored in the Additionally, you can create branches and revert commits just like Remain (it will be a broken symlink) so you know which files are part of the The file for this repository if the USB drive is disconnected, because git-annexĬan't tell whether the file is still actually on the disk.Įven if a file's content is removed, any folders as well as the symlink will Keep in mind that a repository needs to be available in order for git-annex toĮnsure that the data still resides there however. Git-annex: drop: 1 1 /Volumes/MINIDRIVE1/myrepo(master)% (Use -force to override this check, or adjust numcopies.) Rather than dropping this file, try using: git annex move ĭrop Grace-Hopper-Nanoseconds.mp4 (unsafe)Ĭould only verify the existence of 0 out of 1 necessary copies (Recording state in 0 ~/myrepo(master)% cd 0 /Volumes/MINIDRIVE1/myrepo(master)% git annex drop. Move data in a much more fine-grained approach by using the move or copyĬommands, for 0 ~/myrepo(master)% git annex drop. If you don't want the blanket copy that git annex sync -content does, you can
#Git annex documentation iso#
Grace-Hopper-Nanoseconds.mp4: ISO Media, MPEG v4 system, version 0 /Volumes/MINIDRIVE1/myrepo(master)% * git-annex -> 0 /Volumes/MINIDRIVE1/myrepo(master)% file Grace-Hopper-Nanoseconds.mp4 Get Grace-Hopper-Nanoseconds.mp4 (from laptop.) Metadata (the symlink), you can verify this with the file 0 /Volumes/MINIDRIVE1/myrepo(master)% git annex sync -content However, you can see that the content hasn't actually been copied over, only the Lrwxrwxrwx 1 hinmanm staff 198B Dec 20 13:09 0 /Volumes/MINIDRIVE1/myrepo(master)% * synced/master -> laptop/synced/masterĪlready 0 /Volumes/MINIDRIVE1/myrepo(master)% ls -lh (merging synced/git-annex into git-annex.) * master -> 0 ~/myrepo(master)% cd 0 /Volumes/MINIDRIVE1/myrepo(master)% git annex sync (merging usbdrive/git-annex into git-annex.)Ĭompressing objects: 100% ( 13/13), done. Remote: Total 5 (delta 0), reused 0 (delta 0) Remote: Compressing objects: 100% ( 3/3), done.
0 kommentar(er)
