![]() ![]() so its more like a adress book of your data. Git annex dont saves the data itself in git but only the locations and the checksums. (so you see for big files even if git would handle them faster you would waste massivly hard disk space) but again for pdfs a few pictures text files even some office files and stuff 1GB it will not be optimal. you need a central data-store git folder you can use a seperate pc for that or save it on a client, if you use a client for that you have to save the data double on this pc.as many clients you use lets say a projekt with 10 people, each of them have all files and all the history of this projekt/directory on their pc.because at the moment sparkleshare uses git all this disatvantages are there. git as it is has issues with saving/transfairing very big files, and its slow on even mid-sized files lets say 100 5mb big files it would be slow.and its really away, not beeing still there in the history if you use it for movies as example, you would in git annex delete some stuff you want not to see anytime again, so you would delete it everywhere. its not totaly bad for backup, because you can restore old files even if you delete it localy, because it will hold all history.latex.) you would be able to merge this files. if you would as example use it from a laptop in a train without internet and you use a git server in the internet for the central server, and would change some files, then you or somebody else would write on the same txt file as example (html or something.you have a full history, if you delete a file its not gone for ever, so if you change it, the older version is still recoverable.That has a possitive and a negative aspect. at least at the moment, it just uses git for saving the data. and for ascii texts and even a few smaller binary things it works ok.īut it does "to much" for media. I used sparkleshare lately in a project involving 3 computers and 2 people. See also the related software page for software that git-annex is similar to. Git-annex is not the Mercurial largefiles extension.Īlthough mercurial and git have some of the same problems around largeįiles, and both try to solve them in similar ways (standin files using Same repository, which git-annex does, and is an important feature for It does not support keeping different files in different clones of the And while boar supports distributed clones of a repository, ![]() Its own version control system, rather than simply embracing andĮxtending git. Widely distributed storage and partial checkouts.Īlthough it shares many of its goals and characteristics. Which also uses git smudge filters, and appears to lack git-annex's Which also uses git smudge filters, and also lacks git-annex's widelyĭistributed storage and partial checkouts. Partial checkouts of file contents, like git-annex does. It lacks git-annex's support for widely distributed storage, Well see unlocked files) and may be a tighter fit for certain Git-media uses git smudge filters (recently supported in git-annex as Would have still written git-annex instead of using it. I only learned of git-media after writing git-annex, but I probably Involves checking dozens to hundreds of assertions.)Īlthough they both approach the same problem from a similar direction. (Don't beįooled by "make test" only showing a few dozen test cases each test And it has a fairly extensive test suite. I wrote it in Haskell because I wanted it to be solid and to compileĭown to a binary. Git-annex is not some flaky script that was quickly thrown together. With a partial set of files, that are copied around as desired. Git-annex's location tracking allows having many repositories Limitations that might eventually be fixed by efforts like Git-annex is more than just a workaround for git scalability Git-annex is also not a distributed file system like Bittorrent or ipfsīut both are supported as special remotes with more work in making (although syncthing could be supported as a special remote)įiles such a way, with certain limitations (for example, it doesn't Git-annex is also not a folder mirroring system like syncthing Limiting, then git-annex could be a useful alternative. Too slow, or its strict mirroring of everything to both places too Git-annex is not unison, but if you're finding unison's checksumming (There is also a FUSE filesystem built on top of git-annex, called However, the git-annexĪssistant is addressing some of the same needs in its own unique ways. Git-annex is not a filesystem or Dropbox clone. For a backup system that uses git and that git-annex supports It may be a useful component of anĪrchival system, or a way to deliver files to a backup ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |